Why does the rootservices url/document prompt for jazz credentials
I have a customer running 6.0.6.1 on WAS and when they navigate to the https://server:9443/rm/rootservices url they are required to login. This behavior is causing a problem for our OSLC consumer code. They are using Common Access Cards.
Can anyone tell me how I can set up a 6.0.6.1 system deployed on packaged Liberty Profile to secure the rootservices url so I can debug this issue or tell me how the customer can expose the rootservices url without requiring a login.
2 answers
I just tried this on a standard Liberty 6.0.6.1 and there is no login required to access the root services document. As far as I know there has never been a requirement to login to get the rootservices.
Comments
Thank you for the response. I agree, I have never been required to login to access the root services document on any deployment I've done. I'm wondering if the behavior they see is related to using Common Access Cards or could there be a configuration setting, network or ELM, causing this behavior.
I do not know of any mechanism that would password protect the Rootservices. I think it would be desirable to get more information about the setup. For me, even opening the page in the browser works: https://elm.example.com:9443/jts/rootservices
Jims idea is also something to look into.
Is the login related to some customer configured firewall? I have never seen this behavior.
Comments
Definitely sounds like this is unexpected behavior. I will go back to the customer and see if they can get any information from their systems/network team. They are running in a very secure environment and claim that all server access requires a certificate and a pin from their Common Access Card.
Thank you both for your responses, I'll post back when I get more information.
if they have additional means that prevent accessing a servers, you would have to make sure that s satisfied before asking for the rootserices.