You can use this page to identify the authentication and security integration topic that fits your MDriven Turnkey REST scenario.
Choose an integration topic
Authorization determines what an authenticated user or application is allowed to access. Select the topic that matches the identity provider and authentication approach used by your application.
| If you need to work with | Start with | Example |
|---|---|---|
| OpenID Connect | Understanding OpenIdConnect | Your Turnkey application signs users in through an OpenID Connect provider. |
| OAuth 2 | OAuth2 Integration | An external application uses OAuth 2 to obtain access for an integration. |
| ASP.NET Identity | ASP.NET Identity Integration | Your application uses ASP.NET Identity for user identity management. |
| Request headers | Header-Based Authentication | An upstream system supplies authentication information in request headers. |
Plan authorization before exposing a REST service
Define which users or applications need access and which operations each of them may perform. For example, if an integration reads customer data, document whether the integration may also create or change customer data before you configure the authentication mechanism.
Use the authentication and security topics to select the protocol or service that matches the environment. Use the REST integration topics there when the application also connects to external APIs, exposes REST services, or uses web APIs.
CORS
Cross-Origin Resource Sharing (CORS) controls whether a browser-based client from one origin can call a service at another origin. Confirm the required client origins, HTTP methods, and headers with the application owner before applying CORS settings.