Powered by Blogger.
Menu :
Showing posts with label Authentication. Show all posts
Showing posts with label Authentication. Show all posts

Your Google Apps Account, And The New Administrative Google Login

In some cases, the earlier provided procedure, for accessing the limited access domain administrator account, may not work, for your Google Apps domain.

For some Google Apps domains, you will need to reset the password using the Google administrative reset. Instead of the wizard at "accounts.google.com", you may need the administrative reset wizard, at "https://admin.google.com".

A Google Apps administrative account reset uses the same set of displays, as the previously discussed limited access account reset.

When you request administrative account reset, you first try the using default account name.

For my domain, if it had been purchased after November 2012, the default account name would be "bloggeradmin@nitecruzr.net". Yours will be "bloggeradmin@yourdomainURL" - whatever "yourdomainURL" actually is.

Domains purchased before December 2012 will apparently still use a Google Apps token sent in email or linked from Google Wallet.

As previously advised, always use one browser for Blogger and other Google activity like GMail, and the second for the Google Apps session. For best results, first clear cache, cookies and sessions (yes, all 3!), and restart the second browser.

Use the same account name, as advised - just substitute the administrative reset sequence.
https://admin.google.com/


Click on "Need help?".

Select "I don't know my password".

Enter your limited access Google Apps account name.
In most cases, you will go into the expected administrative account reset sequence.

With a mature account, where you have previously setup a custom administrative account, "bloggeradmin@yourdomainURL" may not be accepted. Now, you must try an extended administrative account reset.


If the limited access account, for your domain, is not operational, don't panic.

Return to the previous screen, and select "I don't know my username".

Now, you have other details to provide.


Whether you use the standard administrative reset - or the extended administrative reset - Google will send a password reset email message, to the backup email account associated with the domain. The email account should be the one used by the Blogger account, under which you purchased the domain.

Other than the previously enumerated cases where you can't use the recovery email address, this should be a reasonably straightforward process.
  1. Access the new Google Administrator Login screen.
  2. Click on "Need help?".
  3. Request password reset.
  4. Access the right email account.
  5. Open, and execute the password reset email.
  6. Hopefully, you're done.
  7. If necessary, return to the previous screen.
  8. Select "I don't know my username".
  9. Provide additional details.
  10. Go to Step 3.
Once you're in the Admin Console, you can check / set the auto renewal option setting, or you can retrieve the login instructions to access the registrar's zone editor - or do whatever else you need to do.

The next time you need to access the Admin Console, try to remember the previously set account name and password. And, if you feel up to it, add recovery options to your administrator account.

>> Top

All Mobile Computers Are Not Created Equal

We've seen a few questions about comments, supposedly published - but vanishing, when using a mobile computer, in Blogger Help Forum: Something Is Broken.

This symptom, as reported, reminds us of the long ago reports of "vanishing comments" - but using desktop computers.
At least one of the folks who isn't able to comment said she was attempting to do so from her mobile phone. Is Blogger now losing comments from mobile devices?
The answer here is not quite so ominous, though the situation is still frustrating - to both the blog owner, and the various visitors.

Blogger comments are offered in three "desktop" computer styles, selected by the blog owner.
  • Embedded, positioned below the posts.
  • Full screen, on a separate page.
  • Popup, in a separate, miniature window.
Each of these choices have their own special advantages and disadvantages, which vary in relevance, according to the blog reader population.

On a "mobile" computer - and with the "mobile" template enabled, there is yet a fourth style.
  • Embedded, in a special "mobile" dialogue.

The comment entry process, in general, involves at least four distinct steps.
  • Authentication. Where required by the blog owner, and / or preferred by the blog visitor, the visitor may provide personal identification.
  • Entry. The comment is entered, and edited.
  • Preview. The visitor can view the comment, as entered, before actually publishing it.
  • Verification. Where required by the blog owner, the visitor solves a puzzle, aka "CAPTCHA", to prove that he/she is not using an automated script.
Entry and Preview goes back and forth, at the preference of the comment publisher, until satisfied.

Depending upon the "mobile" computer and template in use, any of the four comment entry styles may be a problem, for any of the four steps identified. If you are familiar with the comment entry process, in general, consider the various controls and objects involved - and when each object is presented to the visitor, attempting to publish a comment.

Consider three different possible ways of presenting the various controls and objects, involved in publishing comments.
  • Everything "visible" simultaneously, with the display zoomed out so everything is visible. On anything but a large screen tablet, you would probably need a magnifying glass, to read the captions, instructions, and labels.
  • Everything "visible" simultaneously, but with most objects off screen, until each is needed. Scrolling is done using finger gestures, not using scroll tabs - and it's never obvious where any "missing" objects may be, at any time.
  • Everything visible in sequence, one step at a time. Extra controls, to move forward and backward in the sequence, are required. To someone not familiar with the comment entry process, in general, some controls may not be obvious.
None of these three options provide perfect solutions. Even being experienced in the commenting process, I have found no obvious excellent choice, when using a "mobile" computer.

Besides the various control and display issues discussed above, consider the effects of cookies and scripts, which may or may not be supported by any given "mobile" computer - and layered security, which is a challenge, on every computer. Both may be a special problem, on "mobile" computers.

Until "mobile" computers are developed, with controls and displays equal to (better than) to those of "desktop" computers, I suspect that there will always be problems with commenting on "mobile" computers - just as there are problems with use of "mobile" computers, and with commenting on all computers, in general.

>> Top