Sign in options for mobile apps – Oomnitza Documentation

You can configure how users sign in to Oomnitza mobile apps.

Oomnitza offers the following mobile apps for performing audits, inventorying assets, and assigning and tracking accessories:

Audit app. Available for Apple mobile phones and iPads.
Assets app. Available for Apple and Android mobile phones.
Stockrooms app. Available for Apple mobile phones.

Tabe: Sign in options for Oomnitza mobile apps

Sign-in options	Assets (Android)	Assets (iOS)	Audit (iOS)	Stockrooms
Oomnitza username and password	Yes	Yes	Yes	No
Google SSO	Yes	Yes	Yes	No
Single sign-on (SSO) with customer's identity provider (IdP)	No	Yes	Yes	No
Web authentication sessions	No	No	Yes	No
Ephemeral web authentication sessions	No	No	Yes	No
Preferred browser	Yes	Yes	Yes	No
Legacy web-view implementation	No	No	Yes	No
Token	No	No	No	Yes

Best practice is to create dedicated roles for accessing mobile apps and assign the role to mobile app users.

Oomnitza username and password

Mobile app users sign in to the app using their Oomnitza username and password.

Google SSO

Users use their Google account to sign in to Oomnitza mobile apps.

SSO

Users use their organizations IdP, such as Okta, to sign in to Oomnitza mobile apps. To choose an option other than the default, which is web authentication session, long tap the sign-in field.

Figure: SSO field

Tip
With the exception of legacy web-view sessions, and depending on the IdP that is used to sign on, more advanced methods of authentication, such as biometric authentication, can be used.

Web authentication sessions. Currently, Safari is the only browser that supports web authentication sessions for iOS devices. To find out the advanced authentication features that are available, refer to the documentation provided by your IdP.
Ephemeral web authentication sessions. Ephemeral web authentication sessions do not use persistent storage for cache, cookies, or credentials which means that users who log out have to re-enter their credentials to log into the app.
Preferred browser. When a user is authorized, the browser prompts the user to open the app. The browser might display the URL containing the authorization token.
- iOS. The web authentication session open in the Safari browser.
- Android. Depending on the device configuration, the user might be able to select a browser to handle authorization or open their preferred browser automatically. A browser will be opened in regular mode with no adjustments for authorization.
Legacy web-view implementation. Some advanced authentication features might not be supported and the IdPs that you use might reject the web-view environment.