Ask MY-Community
Olivier JAOUEN
Olivier JAOUEN

Error 401 when call API whith non human identity (MyAPI)

Resolved

Hello,

We are attempting to authenticate and call the Memority APIs as non-human identities via Postman. To do this, we created a MyApi identity and an associated application, then configured the federation.

OAuth2 authentication works correctly: the token is generated and returned by Postman. However, when calling the Read an identity API endpoint, we consistently receive a 401 Unauthorized error.

We have added the necessary rights to the MyApi identity, but we are wondering whether this type of identity has sufficient permissions to call the endpoints related to reading, creating, and modifying identities, or whether additional configuration is required.

Business Model
1 reply
Best reply by Salomée LEFEVRE

Hello,

Could you perform the following actions:

  • Create a right dedicated to API identities (for example: adm.myApi-features)

  • Grant this right to your API identity via the My API admin role, as well as the sys.api-zone-access right (for the dimension, you can use bum-features, API Guardian Guide)

  • Create a Web Service feature (for example, by duplicating a read feature and renaming it identity-internal-ws-read)

  • Create a Feature Access Policy dedicated to API identities and add the previously created features to it.

  • Log in to the USR portal with your API identity and try to access the feature (for example: baseURL/features/identity-internal-ws-read/AA0000).

  • Finally, log in to Postman and run the Execute a Read Feature request: memority_apiGuard_path/bum/features/identity-internal-ws-read/AA000

    Thank you

View original