4.1.4 RemoteUser

[Mathew, Sunil]

Hi,

I got 3.4.6 docker image working in ECS with idp.authn.flows=RemoteUser set in idp.properties and web.xml with the following configuration:
    <servlet>
        <servlet-name>RemoteUserAuthHandler</servlet-name>
        <servlet-class>net.shibboleth.idp.authn.impl.RemoteUserAuthServlet</servlet-class>
        <init-param>
            <param-name>checkHeaders</param-name>
            <param-value>HBS_PERSON_ID</param-value>
        </init-param>
        <load-on-startup>2</load-on-startup>
    </servlet>

I am upgrading to 4.1.4 and I had a question about setting Remote User. Do I set web.xml to the following:
    <servlet>
        <servlet-name>RemoteUserAuthHandler</servlet-name>
        <servlet-class>net.shibboleth.idp.authn.impl.RemoteUserAuthServlet</servlet-class>
        <init-param>
            <param-name>checkHeaders</param-name>
            <param-value>HBS_PERSON_ID</param-value>
        </init-param>
        <load-on-startup>2</load-on-startup>
    </servlet>

I don’t see a place to set with idp.authn.flows in idp.properties. Do I have to make any other changes to get RemoteUser flow working in 4.1.4?

For context, IdP is protected by CAS for login and injects HBS_PERSON_ID in the header.

Thanks for your help. Regards, Sunil

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20210908/adb42949/attachment.htm>