2.3 OBO Users and configuration
This topic provides information on OBO Users and configuration.
The following 3 users must be created with required functionality / services / roles access in OBO before testing the integration with OBDX. These users are used to invoke OBO services documented in step 3.2. Eureka URL
- OBDX – This user is required for the OBDX/OBRH configuration to call OBO endpoints directly. These calls are made to the OBO host and do not pass through the API Gateway Router.
- OBDXAPI1 – This user is required for the OBDX/OBRH configuration to
communicate with the Document Management System (DMS) also known as Content.
The DMS is used to manage all documents centrally across both OBDX and
OBO. Since both systems use a centralized DMS, maintaining this user and
its permissions is mandatory.
All api-gateway or api-gateway-router requests through the API use this user.
- OBDXUSER – This user is required to access OBO AppShell application login to perform tasks such as verifying product maintenance, managing business processes, acquiring tasks, processing applications, and handling other OBO-related tasks. This ensures that all applications submitted through OBDX are correctly processed and validated within the OBO system.
Note:
- As per the above configuration, DO NOT use OBDX or OBDXAPI1 to log into the OBO application. Doing so could cause API failures within the application, leading to errors such as Bad Credential or Token Expired.
- Ensure that the above three users have access to OBO services and OBRH consumers.
Parent topic: Prerequisites OBO