API Portal 10.5 | webMethods API Portal for Administrators | Configuring API Portal | Configuring User Registration
 
Configuring User Registration
 
Configuring Approval Workflow for User Registration
Assigning Users to the Approver Group
Configuring the Multi-Level Approval Workflow
User Registration Process
Pending Approvals
View and Manage Users
Email Notifications Templates and Tokens
User Registration in API Portal with Social Login
When API Portal visitors decide to use the APIs there, they need to have full access as validated users to log in to the portal. To log in to the API Portal, users can either:
*Register with API Portal by providing an email address and password. Upon approval, API Portal creates an account for the user in the UMC, and the user can log in with the email address and password provided at registration. Users can manage their own account details and change the password from the Profiles link in API Portal.
*Use the social account credentials, for example, Google or Facebook. Upon approval, API Portal notifies the user. At the first login, API Portal creates an account for the user in the UMC. Users who log on to API Portal using social accounts can cannot modify anything except their language preference from the Profilespage.
Depending on your security requirements, you can choose the level of approval needed when registration requests and social logins arrive:
*Approval required. This option is used to define a multi-level approval process to onboard a user. API consumers who would register to the API Portal must be approved by the multiple level of approvers specified in this section. So, you can define more than one level of approval and provide the names of users or user groups that must approve the new user registration at each level.
Note:
Only the users with API Administrator or API Provider privileges can approve user registration. The API Consumers cannot be a part of the user groups that approve user registrations.
When you provide a user group as approver at a level, you can also specify whether a member from the specified user group can onboard the user or all members of the user group must approve the new user. Once the registration is approved by the first level, it is forwarded to the next level, and so on till it is approved by all levels before being onboarded. The user registration request and the approval at each level is notified to the approvers over email.
Note:
Approval workflows in API Portal are separate from the approval workflows that are used with run-time policies in CentraSite.
*Email confirmation (default). Email confirmation provides a simple way to register new users. Upon receiving a user registration request, API Portal sends an email to the requester at the email address provided at registration. The requester clicks the link in the email to activate the user account and the user credentials.
*Automatic registration. If it’s not essential to review each user registration request, you can use automatic registration, where API Portal automatically processes all user registration requests or social log in requests upon receipt. With automatic registration, API Portal creates the user account and notifies the requester by email that their account is activated and ready to use. The requester needs to log in to the portal using the email address or social account credentials that were provided at registration.
By default, API Portal stores all user registration approvals and email notifications. Depending on the volume of user registration activity for your portal, you may want to periodically purge the approval and email notification entries. For more information, see Purging Logs.