Solutions
Archived

401 response using REST API for sub-realm requests in OpenAM 11.0.0

Last updated Jan 5, 2021

The purpose of this article is to provide assistance if you encounter a 401 Unauthorized / Access denied response when using the REST API for sub-realm requests in OpenAM 11.0.0.


Archived

This article has been archived and is no longer maintained by ForgeRock.

Symptoms

The following response is received when performing a sub-realm request using the REST API:

{ "code": 401, "reason": "Unauthorized", "message": "Access denied" }

Recent Changes

 Upgraded to OpenAM 11.0.0

Causes

The REST API authN filters inside of web.xml only authenticate correctly for top level realms.

Solution

This issue can be resolved by upgrading to OpenAM 11.0.1 or later; you can download this from BackStage.

See Also

N/A

Related Training

N/A

Related Issue Tracker IDs

OPENAM-3183 (The forgerock-REST authN filters inside of web.xml only handle top-level-realm use cases)

OPENAM-3277 (Authorization Filter causes the serverinfo/cookieDomains REST endpoint to not be called.)


Copyright and Trademarks Copyright © 2021 ForgeRock, all rights reserved.