OneID enterprise provisioning Provisioning without using a shared secret OneID allows you to easily bring a secure trustable identity to your enterprise. The RP asks for the email address on login and matches up the email address (certified by OneID as belonging to the user) on first login with email addresses in a provisioning file, then uses the public keys for all future logins. That way, if the user's email changes, it doesn't matter, he can still log in. This avoids having to issue usernames and passwords to provision users. You can ask the user for his OneID friendlyname or number. Then use the OneID certification to match up to a database of friendlyname/number, and then remove the database entry and store the UID and public keys for future use. Provisioning with a shared secret You can also give out usernames and passwords, and require user to use these for first time login after hitting the OneID login button. This is convenient if the user already has a legacy username and password. then subsequent logins won't prompt for a username/pwd. RBAC credentials For RBAC, there are a number of options:
|