Authentication and OAuth

Implicit OAuth is a lighter weight version of OAuth designed to be used by systems that do not have, or do not want to use server side components. Implicit OAuth can be implemented entirely in the browser using javascript alone. It is available for members and non-members and works like this: You create a special Continue Reading

If an active access token already exists with the same scopes that your OAuth authorization URL requests, and the user is signed into their ORCID record, they will not be prompted to grant authorization again. Instead they will be taken directly to the redirect URI. If you want to require a user to grant authorization Continue Reading

Any or all of the parameters can be used: ParameterFieldNotesgiven_namesFirst nameThe first name field will be filled in on the registration form if a specified email address or ORCID iD does not match that of an active ORCID record. family_namesLast nameThe last name field will be filled in on the registration form if the specified email address or ORCID iD does not match that Continue Reading

Users can change their display language on their own at any point. The following language settings are available: LanguageCode(Arabic)arčeština (Czeck)csEnglish enEspañol (Spanish)esFrançais (French)frItaliano (Italian)it日本語 (Japanese)ja한국어 (Korean)koPortuguês (Portuguese)ptРусский (Russian)ru简体中文 (simplified Chinese)zh_CN繁體中文 (traditional Chinese)zh_TW Was this helpful?Yes   NoAdditional Comments:Send Feedback

If you are concerned with multiple users being on the same machine and not signing out between sessions, you can force a sign-out before starting the OAuth process. To force a sign-out, send the user to the page https://orcid.org/userStatus.json?logUserOut=true. An optional callback param can be included with the url to trigger a javascript function you specify, Continue Reading