Types of authentication

The vendor application's API determines the type of authentication that is required. To facilitate this, the following types of authentication are supported:

• API key.  API key is used for token-based authentication where you're provided with a single credential such as an API key, an API token, or a static token.
• AWS Auth. AWS Auth is a special type of authentication that is used for integrations with Amazon Web Services (AWS), including retrieving AWS Users and AWS EC2 instances.
• Basic Auth. Basic Auth is used for username and password authentication. 
• Custom OAuth 2.0. You can use OAuth when you add credentials for custom extended integrations.
• OAuth 2.0. OAuth 2.0 authorization is used to enable applications to obtain limited access to user accounts for an HTTP service, such as Google, Salesforce, and Zoom. 
• Session-based. Session Based authentication is used to create a Session ID, which is used to authenticate outgoing requests. 
• Signed request. Signed Request authentication is used to create a unique digital signature, which prevents tampering with a request while it's in transit.

Because the authorization flow varies between vendors, Oomnitza provides a set of preset systems that are configured to use OAuth 2.0, Session-Based, or Signed Request authentication. If you have a system that requires this authentication, and it is not available in the list, contact [e-mail].