cq5 - Should a site that requires authentication always send the WWW-Authenticate HTTP response header? -
i tried access site (an aem author server) always requires authentication. attempting use basic authentication in url in browser address bar, follows: http://admin:admin@localhost:4502/
but when tried that, got following security confirmation (in firefox 38.0.1):
clicking "yes" took me non-authenticated login page, seemingly ignoring basic auth credentials had sent. following questions (and comment on it) helped me understand because aem author server not asking authentication credentials--it not sending www-authenticate http response header:
- how http://user:pass@host.com authentication work?
- why browsers not send authentication header when credentials provided in url?
hence, browser didn't send basic auth credentials had put in address bar.
so led me question why aem author server, requires authentication, isn't sending http www-authenticate header. begs larger question:
for site always requires authentication, reasonable expect site always send www-authenticate response header, or there valid reasons not include header though authentication indeed required?
there different type of authentification application may implement , require. aem not require basic auth (except of aem felix console). cannot expect directly logged in authentification method not supported, not required or not configured. that's why browser notifies no authentification required page. aem uses html page form username , password , authentification request sent backend sling processes further. read more in cq basics or sling authentification docs topic.
Comments
Post a Comment