Configure an Identity Provider in Access Gateway

To integrate Login 3.0 with a machine-to-machine (M2M) application, you need to work with the UPBOND team for registration and configuration. M2M applications, such as command-line tools, daemons, IoT devices, or backend services, interact with APIs via access tokens.

Follow these steps to set up your M2M application:

---

Steps to Register an M2M Application

1. Provide Application Details

   Contact the UPBOND team and provide the following information:

   • Application Name

   • Application Type: Machine-to-Machine

   • API to be authorized

   • Required permissions (scopes) for the API

   • Any additional configuration requirements

2. Authorize API Access

   • Specify the API your application needs to access (e.g., Management API).

   • Define the required scopes or permissions. For example, your application might need the following:

     • read:client, write:client, update:client, delete:client

     • read:users

   The UPBOND team will configure these scopes for your application and associate them with the access token.

3. Obtain Application Credentials

   Once the application is registered:

   • The UPBOND team will provide the Client ID and Client Secret.

   • Save these credentials securely, as they are required to authenticate your M2M application.

---

Application Settings

After the application is created, you will receive configuration details, including:

Tab	Description
Settings	Contains key configuration details for API access, including endpoint URLs and permissions.
Credentials	Includes the Client ID and Client Secret for authenticating your application.
APIs	Lists the authorized APIs for your application, along with their associated scopes.

---

Next Steps

1. Integrate the Credentials

   Update your M2M application code to use the provided Client ID and Client Secret for authentication. If required, the UPBOND team can supply example integration code.

2. Use Login 3.0 APIs

   Use the Login 3.0 APIs for your application's needs:

   • Authentication API: Handles token issuance and authentication for API calls.

   • Management API: Allows for automation of tasks like managing users and configuring grants.

3. Test the Integration

   Validate that your application can:

   • Authenticate with Login 3.0.

   • Obtain and use access tokens to interact with the authorized API.

4. Deploy the Integration

   Once testing is complete, deploy your application with the configured Login 3.0 integration.