Currently, the mobile apps from Atlassian use a non-standard browser user agent that is identified as AtlassianMobileApp and the request is that the app be built using a Standard browser user agent that supports Javascript/JQuery.

This is to resolve Issues with the SAML SSO within the Mobile app due to non-standard user agent support or coding like JQuery.

When a user goes through the application and tries to Authenticate, the application automatically re-directs the user to our SAML Identity provider. The SAML provider requires that the application support Javascript/JQuery in order for the application to authenticate properly. In customer case, they use a method called P2A (Push 2 Authenticate) and presents the user a letter or number. This requires the use of the SecureAuth Authenticate application. If a user authenticates with the SecureAuth application, the user is presented with the message of "Unfortunately, an access issue has occurred. Your session may have timed out or you may have started from and incorrect favorite."  (attaching an image of this error)

There is a way to select another option when the current method does not work by clicking on a link in the Authentication flow with the message: "Didn't recieve your PIN? Try another delivery method" However, when the link is clicked in the authentication flow, within the Confluence server or Jira server mobile app, the link is not activated and does not re-direct. (attaching an image of this error)

Customer Identity team identified that the application user_agent is coming through as AtlassianMobileApp and the SecureAuth application requires a standard user agent that is supported by major browsers on mobile devices and will execute js files. Users are able to login to Jira or Confluence via a browser without issue, but that defeats the purpose of the mobile app.