Authentication
Spotfire provides several standard authentication methods, as well as custom authentication using APIs.
Authentication method | Description |
---|---|
User name and password | The default method. User name and password specifies authentication using HTML forms (POST - application/x-www-form-urlencoded ) or BASIC access authentication. The credentials are checked against the
Spotfire database or another external authentication source (such as LDAP, Windows NT Domain, or Custom JAAS). See
External directories and domains and
User name and password authentication methods.
|
Two-factor | You can combine the chosen primary authentication method with X.509 client certificates. See Two-factor authentication. |
NTLMv2 | Note that NTLMv1 is not supported. See NTLM authentication. |
Kerberos | See Kerberos authentication. |
Anonymous | If enabled, limited access to view Spotfire files is allowed for unauthenticated sessions. See Configuring anonymous authentication. |
X.509 client certificates1 | Spotfire Server requires the client to provide a valid X.509 certificate. Requires HTTPS. See Authentication using X.509 client certificates. |
OpenID Connect | Goes under the label "Web Authentication" in Spotfire. Provides integration with external authentication providers that support OpenID Connect. See Configuring OpenID Connect. |
External authentication | See APIs and extension points. |
Custom Web Authentication | See APIs and extension points. |
Custom Authentication | See APIs and extension points. |
- User Directory Options
Spotfire features the following user directory sources for authentication. - APIs and Extension Points
To create a custom authentication experience for your Spotfire users, you can use one of the following types of APIs or extension points.
Parent topic: Authentication and Authorization
Related concepts
1 Combining X.509 client certificates with another authentication method such as user name and password provides a type of two-factor authentication.