Stonefield Query supports external authentication with Active Directory Federation Services or OpenID Connect. In addition, you can also enable support for external authentication via Google, Facebook, or Twitter social media accounts. Each of these authentication options can be configured by entering the appropriate information in the Configuration Settings section of the project.
To enable external authentication using Active Directory Federation Services, you need to specify the ADFS Metadata address and the ADFS Realm.
ADFS Metadata address: A URL that points to the active directory instance to perform the authentication. For example, for the Stonefield domain: https://stonefield.local/FederationMetadata/2007-06/FederationMetadata.xml
ADFS Realm: For the realm address, use the WS-Federation Passive protocol URL that was entered when configuring ADFS. This is usually the URL for Stonefield Query.
To enable external authentication using OpenID Connect, you need to specify the OpenID Authority, the OpenID ClientID and the OpenID ClientSecret.
OpenID Authority: A URL that points to the authentication server that supports the OpenID Connect protocol.
OpenID ClientID: The ClientID value to send to the OpenID Connect authentication server.
OpenID ClientSecret: The secret key value to send to the OpenID Connect authentication server.
To enable external authentication using Facebook, you need to specify the Facebook AppID and the Facebook AppSecret. Refer to the developer documentation for details on creating an App that supports authentication.
To enable external authentication using Google, you need to specify the Google ClientID and the Google ClientSecret. To generate those values, navigate to Integrating Google Sign-In into your web app and select CONFIGURE A PROJECT.
To enable external authentication using Twitter, you need to specify the Twitter ConsumerKey and the Twitter ConsumerSecret. To generate those values, navigate to https://apps.twitter.com/ and create a new app for use with authentication.
© Stonefield Software Inc., 2019 • Updated: 04/30/19
Comment or report problem with topic