Registering Your App
How to register your application
Last updated
How to register your application
Last updated
IDPartner follows a two-stage production process for integrating with the services. It involves setting up a sandbox application first, followed by accessing the production environment. Here are the details of each stage:
Sandbox Application:
To begin, you need to set up a sandbox application with IDPartner.
The sandbox application provides access to IDPartner's sandbox banks and allows you to integrate with the OIDC API.
Integration with IDPartner's services follows the standard OIDC protocol, ensuring compatibility and interoperability with various identity management systems.
You have the flexibility to choose from a range of libraries and SDKs available in your programming language to implement the integration smoothly.
Production Access:
Once you have successfully tested and developed your integration in the sandbox environment, you can move on to the production stage.
Production access uses the same API as the sandbox; however, it requires mutual TLS for obtaining identity information.
During the onboarding process for production access, you will be required to request a certificate.
Once you have obtained the certificate, you can use it for authentication and gain access to the production environment.
Application name
This is the name of your client application that will be displayed to users during the identity provider selection and consent process. Choose a name that accurately represents your application.
Application logo
You'll need to provide the URL pointing to the logo image of your client application. This logo will be displayed alongside your application's name during the authorization process.
Origin URL
The Origin URL is specifically used with the IDPartner Button. When a user clicks on the IDPartner Button, they will be redirected to this URL to initiate the authorization flow with a confidential client. Ensure that the Origin URL is set correctly to ensure a seamless user experience.
Redirect URL
Redirect URLs are the URIs that your client application uses to receive a response from the authorization endpoint of the Identity Provider.
You have the option to provide a JWK Set (JSON Web Key Set) for enhanced security in your IDPartner integration. JWK Set helps encrypt and sign requests, ensuring message authenticity, integrity, and confidentiality within the OpenID Connect flow. While optional, implementing JWK Set strengthens security by preventing repudiation, protecting against tampering, and ensuring messages are accessible only to authorized recipients. For more information on JWK Set and generating them.
Please note that the use of JWK Set is optional and depends on your specific security requirements.
JWK Set URI
This is the URL pointing to the JWK Set of your client application.
The JWK Set contains public keys for encryption and signing purposes.
JWK Set Content
This refers to the actual content of the JWK Set (JSON Web Key Set) for your client application.
Do not include private keys in the JWK Set for security purposes.
