Seeq offers a variety of mechanisms for authenticating to Seeq. This page describes the reasons to use, or not use, each of the options.
Mechanism | Recommended For | Reasons to Use It | Reasons Not to Use It |
---|
Seeq Directory | Demos, test systems, smaller organizations | | |
LDAP | Larger organizations | Simple username & password authentication synced with Active Directory or an LDAP server. Users automatically gain or lose access to Seeq based on group membership. Users can access Seeq without being connected to the corporate intranet. Does not require Windows.
| |
Windows Authentication | Larger organizations | | Requires coordination with IT administrators: creating an AD user for Seeq, creating an SPN. Requires either Seeq or a remote agent inside the corporate intranet and running Windows.
|
OpenID Connect | Larger organizations | Web-style single sign-on authentication synced with an external directory: Azure Active Directory, Okta, many others. Users automatically gain or lose access to Seeq based on their access to the external directory. Users can access Seeq without being connected to the corporate intranet. Does not require Windows.
| Requires coordination with IT administrators: configuring the OpenID Connect provider. Not all external directories support limiting access to specific groups/accounts. Azure Active Directory does, others may not. Requires that either Seeq or a remote agent has access to the OpenID Connect provider.
|
Windows Authentication (via the LDAP Connector) | - | | |
Users of the Seeq SDKs will need to use either Seeq Directory or generate an access key.