I’ve been trying for about a week now to validate my access tokens with no luck. Today I happened to find a message buried deep in my Tomcat system logs that complains about an Okta cookie that was returned from the SSO Widget. The message was (All of the state- and site-specific fields have been obfuscated.):
INFO: A cookie header was received [responseType":["id_token","token","code"],"state":"#####","nonce":"#####","scopes":["openid","email","profile"],"urls":{"issuer":"https://dev-#####.oktapreview.com","authorizeUrl":"https://dev-#####.oktapreview.com/oauth2/v1/authorize","userinfoUrl":"https://dev-#####.oktapreview.com/oauth2/v1/userinfo"}}; okta-oauth-nonce=#####; okta-oauth-state=#####] that contained an invalid cookie. That cookie will be ignored.Note: further occurrences of this error will be logged at DEBUG level.
I’m not exactly sure why it’s complaining about the cookie, but the fact that the “responseType” keyword has a closing quote but no opening quote, and also the double close-curly-braces after the urls section both seem a little problematic.
Has anyone else seen this?