Has anyone successfully been able to get SAML SSO working with Maximo Mobile when ADFS is used as the identity provider? I've looked into this on and off over the years and it was last left with support with an enhancement request, but figured I'd check to see if anyone has found any workaround.
From what I've gathered, the inappbrowser invoked by Mobile when getting the SAML token isn't compatible with Kerberos, which ADFS is still using prior to sending back the SAML response. It seems odd that my organization would be an outlier with that config, but maybe.
Our SAML implementation works fine with the normal apps - it just comes to a stop in Mobile as soon as authentication is passed off to ADFS and the windows integrated authentication endpoint. My current workaround to use mobile is to setup a separate JVM that uses maximo authentication and have users go the normal username/password route.
------------------------------
Brandon Fisher
------------------------------