<< Click to Display Table of Contents >> Raynet One Data Hub > 14.0 > Connectors > Alphabetic Connector List > Microsoft Azure AD > Connector Parameters Authentication |
This parameter represents the endpoint of the server.
Technical Name |
server_url |
Category |
Authentication |
Type |
String |
Default Value |
https://graph.microsoft.com |
Example Values |
https://graph.microsoft.com |
•Documentation on beta endpoint reference
This parameter should contain the client ID which is associated with the account and together with the client secret part of the credentials used for the OAuth2 authentication.
Technical Name |
client_id |
Category |
Authentication |
Type |
String |
Default Value |
n/a |
Example Values |
In order to execute the connector it is required to set up an authorized app (service principal) in Azure that has been assigned the Reader role. The simplest way to achieve this is to use the Azure command line interface (CLI) like described in the official documentation. The response contains the necessary credentials:
•appId (clientId)
•password (clientSecret)
•tenantId (this is the ID of the underlying Azure Active Directory)
This parameter should contain the client secret that has been generated for the app in the app registration portal.
Technical Name |
client_secret |
Category |
Authentication |
Type |
String null |
Default Value |
null |
Example Values |
null |
Supply EITHER a Client Secret OR (a Private Key AND a Certificate). In order to execute the connector it is required to set up an authorized app (service principal) in Azure that has been assigned the Reader role. The simplest way to achieve that is to use the Azure command line interface (CLI) like described in the official documentation. The response contains the necessary credentials:
•appId (clientId)
•password (clientSecret)
•tenantId (this is the ID of the underlying Azure Active Directory)
This parameter contains the private key associated with the public key to the account.
Technical Name |
private_key |
Category |
Authentication |
Type |
String null |
Default Value |
null |
Example Values |
null, -----BEGIN PRIVATE KEY----- MIIEwAIBADANBgkqhkiG9w0BAQEFAASCBKowggSmAgEAA oIBAQD8pNLKhayHFAJ1ey5nTUGa9wPzOwjlmCgiLbyzw2 2wQrhCBT+DMa24+iSAKHE72lgK5/OQOTbIPFWP ... vSlewskdmlsKXZ1hPG20JotkFG7jEz8fKTV4BgTmqWIyQ Xx/U4aNjoXBLzyvf1t4 -----END PRIVATE KEY----- |
This parameter contains the X.509 certificate registered with the account.
Technical Name |
certificate |
Category |
Authentication |
Type |
String null |
Default Value |
null |
Example Values |
null -----BEGIN CERTIFICATE----- MIIEwAIBADANBgkqhkiG9w0BAQEFAASCBKowggSmAgEAA oIBAQD8pNLKhayHFAJ1ey5nTUGa9wPzOwjlmCgiLbyzw2 2wQrhCBT+DMa24+iSAKHE72lgK5/OQOTbIPFWP ... vSlewskdmlsKXZ1hPG20JotkFG7jEz8fKTV4BgTmqWIyQ Xx/U4aNjoXBLzyvf1t4 -----END CERTIFICATE----- |
During the generation of the Private Key, an associated public key (certificate) was written to the file 'cert.pem'. On the Azure Portal, the certificate must be registered for the Application of the Azure AD. Follow the official documentation for the detailed description. This parameter must be set to the content of the certificate (the file 'cert.pem'). The certificate can be shared with anybody and cannot be abused for authentication.
This parameter contains the directory tenant that permission shall be requested from. This can be in a GUID or friendly name format.
Technical Name |
tenant |
Category |
Authentication |
Type |
String |
Default Value |
n/a |
Example Values |
|