Create an authentication profile
Create an authentication profile and add one or more authentication policies to the profile. You can also configure the ID Token and OAuth Token authentication profiles that are available by default.
Before you begin
Role required: api_service_admin, adaptive_auth_policy_admin
Note: You can apply authentication policies, IP range, role-based, user-based, and so on with mutual authentication and customized authentication.
Procedure
Navigate to All > System Web Services > API Access Policies > Inbound Authentication Profiles.
Select New.
The system displays the message.
What kind of authentication profile?Select Create standard http authentication profiles.
On the form, fill in the fields.
Field Description Name Name to identify the authentication policy. Description Description of the authentication policy. Active Option to make the authentication policy active. Application Scope of the authentication policy. Type Type of the authentication available. You can select Basic Auth, ID Token, Certificate based Auth, or OAuth. OAuth Entity OAuth Entity profile. This field appears only when ID Token or OAuth is selected from Type. Double-click Insert a new row.
Select an authentication policy from the list and select the save icon
save icon.
**Note:** Don’t select Allow Access Policy or Deny Access Policy. These policies are meant only for user logins.
You can add one or more authentication policies for an authentication profile.
**Note:**
Authenticate Header \[WWW-Authenticate\].
When REST API Access Policy is active we will return the most recently mapped authentication profile in the authenticate header. In the case you want the server to return all the authentication schemes, use the `glide.security.response.authenticate.header.auth_profile.first_scheme_only` property and set it to **false**. The response is returned with multiple header. For example:
```
< WWW-Authenticate: BEARER realm="Service-now"
< WWW-Authenticate: BASIC realm="Service-now"
```