What authentication types are available for event triggers in SailPoint?

• A. Username/Password, API Key, OAuth 2.0, None
• B. Basic Auth, Bearer Token, None
• C. Token-based Auth, Digest Auth, OIDC
• D. Single Sign-On, API Token, Basic Auth

Answer: (B)

In SailPoint, the available authentication types for event triggers are focused on methods that facilitate secure communication between services while activating specific workflows or operations. Basic Auth and Bearer Token are commonly recognized authentication schemes suitable for event triggers.

Basic Authentication uses a straightforward scheme where the user's credentials (username and password) are presented in a base64 encoded format. While this method is simple, it is essential to be used over a secure HTTPS connection to protect the transmitted credentials.

Bearer Token authentication involves the use of a token that grants access to resources. This token is typically generated upon successful authentication and is included in subsequent requests to access protected resources. This method is widely used due to its ease of implementation and better security practices compared to transmitting user credentials directly.

Other options do not accurately reflect the primary authentication methods relevant to event triggers in SailPoint. Token-based Auth and Digest Auth may be valid in different contexts but are not explicitly listed among the standard methods for triggering events. Similarly, while Single Sign-On and API Tokens are important concepts, they don't specifically represent the authentication types defined for event triggers within the SailPoint framework. Thus, the answer reflects the most commonly utilized and relevant authentication mechanisms in the context of event handling.