I've installed ga_login & mobile_codes -dev versions. Works well so far.

I notice that the key ID that's created is in the form:

otpauth://totp/@?secret=################

In Google Authenticator, it shows up under account == "@"

Since I 'stage' my from a development to a production site, I have the same user and site_name.

But I *do* want to have a different GA code for production.

To prevent confusion, it'd be useful to be able to specify an additional 'textID' when creating the GA code in the Drupal UI for a user -- so that, e.g., the code generated, and the account name used, are, instead:

"@:"

or something similar.

Comments

that's annoying - tag-usage was stripped, and no option to edit? take 2 ...

I've installed ga_login & mobile_codes -dev versions. Works well so far.
I notice that the key ID that's created is in the form:
otpauth://totp/[user]@[site_name]?secret=################
In Google Authenticator, it shows up under account == "[user]@[site_name]"
Since I 'stage' my from a development to a production site, I have the same user and site_name.
But I *do* want to have a different GA code for production.
To prevent confusion, it'd be useful to be able to specify an additional 'textID' when creating the GA code in the Drupal UI for a user -- so that, e.g., the code generated, and the account name used, are, instead:
"[user]@[site_name]:[textID]"
or something similar.

Status:Active» Fixed

We added a variable that can be set with variable_set:

<?php
variable_set
('ga_login_textid', 'MyTeXtId');
?>

or in settings.php in the $conf variable:
<?php
$conf
['ga_login_textid'] = 'MyTeXtId';
?>

We chose not to make it available through the interface, because changing it will render all created logins useless.

Thanks! Works nicely!

Thanks! Works nicely!

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.