cancel
Showing results for 
Search instead for 
Did you mean: 
cancel

Who Me Too'd this topic

CER v15 vs v14 authenticate API

rmaslanka2
Level 1
Level 1

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?

Who Me Too'd this topic