> For the complete documentation index, see [llms.txt](https://docs.ascertia.com/signinghub-web/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ascertia.com/signinghub-web/registration-and-login/login-and-authentication-methods/login-through-oidc.md).

# 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 account <a href="#login_through_your_supported_oidc_supported_account" id="login_through_your_supported_oidc_supported_account"></a>

1. Go to the SigningHub login screen.
2. Click the "More Login Options" link available at the bottom of the login screen.\
   A dialogue box will appear listing all the supported authentication methods.
3. Click the "OIDC Configured profile" option.\
   The configured app will appear in a popup.
4. Specify your ID and password in the app.\
   The email address field is automatically populated. If a login hint is configured in the OIDC connector, the configured email address is pre-populated. Otherwise, the email address selected/entered on the SigningHub log-in screen is used.
5. Click the "Login" button.\
   SigningHub permissions screen will appear.
6. 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:

1. **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.
2. **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.
3. **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.
4. **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.

{% hint style="info" %}

1. As a part of GDPR compliance, the "Service Agreement" dialogue box will appear after successful user authentication. This dialogue box contains the links to the "Terms of Service" and "Privacy Policy" pages. SigningHub will ensure that you agree to them before letting you use your account.
2. The "Service Agreement" dialogue box will not appear after successful user authentication if no Service Agreement is marked active.
3. When using an on-premises installation of SigningHub and this is the only configured authentication for the end-users, then you won't need to click the "More Login Options" link to choose it. In that case, this authentication method will be invoked by default on the Login screen.
4. Users cannot log in to SigningHub if their account is disabled, marked as dormant, or temporarily locked due to multiple invalid login attempts.
   {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ascertia.com/signinghub-web/registration-and-login/login-and-authentication-methods/login-through-oidc.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.