09-26-2024 10:16 AM
When working with DevNet Sandbox CER v14, authentication works as described in the API documentation.
A request to /authenticate/status/ returns a 401, a CER 401 page, along with a JSESSIONID cookie.
A second request to /authenticate/status/ while passing that cookie, returns a 200 and <authentication><status>Authentication successful on publisher </status>...
When testing the same on my v15 environment:
A request to /authenticate/status/ returns a 200, <authentication><status>Authentication failed on publisher </status>..., along with a JSESSIONID cookie.
A second request to /authenticate/status/ while passing that cookie, returns a 200 again and <authentication><status>Authentication failed on publisher </status>... again.
Can anyone confirm how they are authenticating to CER v15 APIs and / or if there has been a change from v14 to v15?