uaadmin password change --- roles not being assigned 9205

401 and 9205 errors

I'm working on setting up https with f5, so it is possible this is due to https not being fully configured with OSP

Question: Once https is configured, do we need to change all drivers to also connect in via https, such as a driver assigning roles, dcs, userapp, etc? I believe another client had it working with just port 8180, even after https was configured. Can we still do this with 4.5.6 and the latest OSP version?

I already tried changing the named password for the account.

thanks,
Fred
  • This depends on whether or not you want to restrict the application to only receive http(s) requests from the F5 or not.....if you don't, then anyone (or any system/driver) would still be able to his the original ports....
  • On 30.11.2017 04:04, fp IDMWORKS wrote:
    >
    > 401 and 9205 errors
    >
    > I'm working on setting up https with f5, so it is possible this is due
    > to https not being fully configured with OSP
    >
    > Question: Once https is configured, do we need to change all drivers to
    > also connect in via https, such as a driver assigning roles, dcs,
    > userapp, etc? I believe another client had it working with just port
    > 8180, even after https was configured. Can we still do this with 4.5.6
    > and the latest OSP version?


    The SOAP endpoints in IDMProv still use Basic Auth. So the RRS and UA
    drivers don't talk to OSP and can still use plain HTTP (if you haven't
    disabled the listener in tomcat).
    All the REST endpoints require OAuth2. So a proper OSP config is
    required for the DCS driver.

    >
    > I already tried changing the named password for the account.
    >
    > thanks,
    > Fred
    >
    >



    --
    Norbert