Expand my Community achievements bar.

Learn about Edge Delivery Services in upcoming GEM session
SOLVED

j_security_check is giving j_username and j_password does not match error

Avatar

Level 5

we are using Aem 6.5.16, we have login implementation using an OOTB authentication handler.

We are able to login from the publisher instance but not through the dispatcher. We can see that the login-token cookie is getting set on the publisher, not in the dispatcher. we have allowed all the required configurations at the dispatcher level. 

 

Please suggest.

1 Accepted Solution

Avatar

Correct answer by
Employee

1. check if you are caching request headers.

2. check if you are ignoring the query param.

3. check if you are using /sessionmanagement

View solution in original post

5 Replies

Avatar

Employee

The /clientheaders property defines a list of HTTP headers that Dispatcher passes from the client HTTP request to the renderer (AEM instance).

By default Dispatcher forwards the standard HTTP headers to the AEM instance.

you can configure this like -

/clientheaders
{
"CSRF-Token"
"X-Forwarded-Proto"
"referer"
"user-agent"
"authorization"
"from"
"content-type"
"content-length"
"accept-charset"
"accept-encoding"
"accept-language"
"accept"
"host"
"if-match"
"if-none-match"
"if-range"
"if-unmodified-since"
"max-forwards"
"proxy-authorization"
"proxy-connection"
"range"
"cookie"
"cq-action"
"cq-handle"
"handle"
"action"
"cqstats"
"depth"
"translate"
"expires"
"date"
"dav"
"ms-author-via"
"if"
"lock-token"
"x-expected-entity-length"
"destination"
"PATH"
}

Avatar

Correct answer by
Employee

1. check if you are caching request headers.

2. check if you are ignoring the query param.

3. check if you are using /sessionmanagement

Avatar

Level 5

the current issue is only happening in one of the environments and working fine in all other environments. We are unable to track what is the exact issue with the dispatcher.

Please suggest.