Identity & Access Management
Members are onboarded to SahamatiNet by creating a entity profile, with at least one user designated to manage the member or entity profile and secret.
Here are the steps for a member to onboard.
User Account Activation:
During onboarding, the designated user will receive an email with a link to verify their email address. Once verified, the user will be prompted to set up a password, finalizing the account activation process. Here are the main steps for activating a user account:
Member (Entity) Activation:
To fully activate a member on SahamatiNet, at least one associated user must be activated. This user will then begin the process of generating a secret, which is crucial for future API interactions. The key steps for member activation are as follows:
Once the member onboarded on SahamatiNet, the below APIs can be used by the associated user to manage the secret.
Scenario: Member Secret Management
Generate User Access Token: Use the User Token Generate API by providing email and password to get the access token. The access token should be used as the Authorization token for the steps below.
Reset Member Secret: Use the Secret Reset API by providing the entityId and Authorization token.
Read Member Secret: Use the Secret Read API by providing the entityId and Authorization token to fetch the latest secret to use.
Below are the Base URL of each environment to use IAM APIs.
Production
https://api.sahamati.org.in/iam
UAT
https://api.uat.sahamati.org.in/iam
Sandbox
https://api.sandbox.sahamati.org.in/iam
Token Generation APIs:
API Postman Collection:
Below is the Sandbox Environment file for SahamatiNet Services
To generate a User Access Token, the user must provide their username (email) and the password configured during the account activation process. This access token is necessary for interacting with the member's secret management APIs. The access token has an expiry of 180 days. Below is the API specification.
User email.
The password associated with the user.
curl -L \
-X POST \
'https://api.sandbox.sahamati.org.in/iam/v1/user/token/generate' \
-H 'accept: application/json' \
-H 'Content-Type: application/x-www-form-urlencoded' \
-d 'username=<email>&password=<password>
{
"ver": "1.0.0",
"timestamp": "2024-07-16T11:33:34.509Z",
"txnId": "f35761ac-4a18-11e8-96ff-0277a9fbfedc",
"accessToken": "",
"expiresIn": 86400,
"tokenType": "Bearer"
}To generate a Member (Entity) Access Token, the client ID and Secret are required. The API generates the token with a warning if the secret is within the grace period, but it will fail once the grace period has ended. This token is used for interactions with other members and has a validity of 24 hours. The API specification is detailed below.
The entity ID.
The secret associated with the entity.
curl -L \
-X POST \
'https://api.sandbox.sahamati.org.in/iam/v1/entity/token/generate' \
-H 'accept: application/json' \
-H 'Content-Type: application/x-www-form-urlencoded' \
-d 'id=<id>&secret=<secret>
{
"ver": "1.0.0",
"timestamp": "2024-07-16T11:33:34.509Z",
"txnId": "f35761ac-4a18-11e8-96ff-0277a9fbfedc",
"accessToken": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
"expiresIn": 86400,
"tokenType": "Bearer"
}Member Secret Management APIs
The Reset Secret API is designed to allow an admin to reset a member's secret. To perform this action, an access token with administrative privileges for the specified member is required. Once reset, the newly generated secret will have a validity period of 180 days by default, after which it will need to be renewed or reset again.
With the latest enhancements, members can now select their desired validity period for secrets, up to a defined maximum limit (default: 180 days). The specified validity period is compared with the admin access token expiry, and the minimum value is applied to ensure authentication and security. Additionally, a grace period of 5 days is provided to facilitate a seamless transition between old and new secrets.
Below is the API specification.
User Bearer token for authorization
1.0.02024-07-16T11:33:34.509Zf35761ac-4a18-11e8-96ff-0277a9fbfedcaa-1Specifies the number of days before the secret expires. This field is optional; if not provided, a default value will be used.
100POST /iam/v1/entity/secret/reset HTTP/1.1
Host: api.sandbox.sahamati.org.in
Authorization: text
Content-Type: application/json
Accept: */*
Content-Length: 142
{
"ver": "1.0.0",
"timestamp": "2024-07-16T11:33:34.509Z",
"txnId": "f35761ac-4a18-11e8-96ff-0277a9fbfedc",
"entityId": "aa-1",
"secretExpiryDays": 100
}{
"ver": "1.0.0",
"timestamp": "2024-07-16T11:33:34.509Z",
"txnId": "f35761ac-4a18-11e8-96ff-0277a9fbfedc",
"entityId": "aa-1",
"secret": "xxxxxxxxxxxxxxxxxxxxx",
"expiresOn": 1725010763,
"expirationDate": "2024-12-17T07:10:52.929"
}The Read Secret API enables admin to retrieve the current secret for a specific member. To access this information, an user access token with administrative rights must be provided. Below is the API specification.
User Bearer token for authorization
1.0.02024-07-16T11:33:34.509Zf35761ac-4a18-11e8-96ff-0277a9fbfedcaa-1Specifies the number of days before the secret expires. This field is optional; if not provided, a default value will be used.
100POST /iam/v1/entity/secret/read HTTP/1.1
Host: api.sandbox.sahamati.org.in
Authorization: text
Content-Type: application/json
Accept: */*
Content-Length: 142
{
"ver": "1.0.0",
"timestamp": "2024-07-16T11:33:34.509Z",
"txnId": "f35761ac-4a18-11e8-96ff-0277a9fbfedc",
"entityId": "aa-1",
"secretExpiryDays": 100
}{
"ver": "1.0.0",
"timestamp": "2024-07-16T11:33:34.509Z",
"txnId": "f35761ac-4a18-11e8-96ff-0277a9fbfedc",
"entityId": "aa-1",
"secret": "xxxxxxxxxxxxxxxxxxxxx",
"expiresOn": 1725010763,
"expirationDate": "2024-12-17T07:10:52.929"
}Was this helpful?