Handling 409 Http staus code in OpenIG routes

This topic has 0 replies, 1 voice, and was last updated 3 years, 8 months ago by srinath.m.

  • Author
  • #23837

    Hi All,
    Our client application uses REST API’s to call back end server via OpenIG routes. In some cases, back end server gives 409 response code on some REST API, but OpenIG sends this response to client as 500 Internal server error. Below is the piece of code of the route.

                                                                            "condition": "${request.headers['FilterStatus'][0] == 'SESSIONEXPIRED'}",
                                                                            "handler": {
                                                                                    "name": "SessionExpiredFilterHandler",
                                                                                    "type": "StaticResponseHandler",
                                                                                    "config": {
                                                                                            "status": 401,
                                                                                            "reason": "Session expired",
                                                                                            "entity": "<html><h2>${request.headers['ErrorMessage'][0]}</h2></html>"

    Any idea how to handle 409 response code in OpenIG route ?


Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.

©2022 ForgeRock - we provide an identity and access platform to secure every online relationship for the enterprise market, educational sector and even entire countries. Click to view our privacy policy and terms of use.

Log in with your credentials

Forgot your details?