Login through OIDC
SigningHub gives you an option to use your IDP credentials (OIDC supported protocol) to log into SigningHub. In this case, you don't even need to have a SigningHub ID, as your personal account will be used for SigningHub authentication.
However, logging in through your personal credentials for the first time, will take you to the registration screen and display your personal (email address) for new registration. After registration you can easily login through your personal credentials.
Login through your supported OIDC supported account
- Go to the SigningHub login screen.
- Click the "More Login Options" link available at the bottom of login screen.
A dialog will appear listing all the supported authentication methods. - Click the "OIDC Configured profile" option.
Configured app will appear in a popup. - Specify your ID and password in the app.
- Click the "Login" button.
SigningHub permissions screen will appear. - Click the "Accept" option.
You will be authenticated into SigningHub.
OIDC user profile information NID sync with SigningHub NID
When syncing a user's National Identity (NID) and email from OpenID Connect (OIDC) with SigningHub, actions vary based on whether the user already exists in the SigningHub system:
- If both email and NID are received from OIDC and the user exists in SigningHub: The user will log in, and the NID in the [User] table will be updated with the new NID from OIDC. If the user does not yet exist, they will be registered in the system, and their NID will be added to the [User] table.
- If only the email is received from OIDC and the user exists in SigningHub: The user will simply log in. If the user does not exist, they will be registered.
- If only the NID is received from OIDC and the user exists in SigningHub: SigningHub will search for a user with the received NID. If found, the user will log in, and their NID in the [User] table will be updated. If the user does not already exist in SigningHub, an error will be shown, as the user must already be present in the UserIdentity or [User] table for NID-only syncs.
- If neither email nor NID is received from OIDC: An error will be returned in both cases, as the user must already be present in the UserIdentity or [User] table to proceed with syncing.
|
See Also
- Login through SigningHub ID
- Login through Microsoft Active Directory
- Login through Salesforce
- Login through Microsoft ADFS
- Login through Microsoft Office 365
- Login through LinkedIn
- Login through Google
- Use OTP as two-factor authentication
- Login through SSL client
- Login through Freja Mobile
- Login through Freja eID
- Login through Bank ID
- Login through itsme
- Login through Azure Active Directory
- Corporate logins
- Login through generic OAuth2
- Login through Azure SAML-based SSO