Let’s get started with the guide for Skedler Reports Single sign-on with OpenId and Azure Active Directory. We will go through the step by steps process required to install and setup the Skedler Reports Single sign-on with OpenId connect and generate automated reports.
Download the latest version of Skedler Reports from the Download page
- Go to the config folder using the command cd config.
- Open reporting.yml, and follow the below steps,
1. uncomment the anonymous_access as shown below
# the variable and set the value to `false`. By default, the variable value is set to `true`.
2. Navigate to Skedler Reports SSL Settings, Uncomment the following,
#Enables SSL and paths to the PEM-format SSL certificate and SSL key files, respectively
#These settings enable SSL for outgoing requests from the Skedler server to the browser.
3. Now navigate to the bottom of the page and uncomment the below
#For enabling Active Directory uncomment the sso and change the value true, Default: false
#For OpenIDConnect uncomment the ssoType. (Currently we support only openidconnect)
#uncomment the identityMetadata and replace the <tenantID> with your tenantID
#Specify your clientid from Active Directory
4. Then save the reporting.yml file and start Skedler Reports, open the following link in the browser,
5. Login to azure ad and open the Authentication tab in app registrations and enter the redirect URL as https://localhost:3000/skelder/login and save it.
You can now see the below as shown in the screenshot, and click sign in SSO
6. Enter the login credentials for signing in SSO as shown below,
7. Initially, you will see the data source configuration screen and then you need to confirm your data source as Elastic search and Kibana with its URL,
8. Scroll down enable authentication and select the authentication type as Open distro and Enable Kibana User Authentication for Report Generation then Select SSO type as OpenID connect and enable Multi-tenancy for Report Generation. Then enable global and private tenants if needed. Enter the super admin user name and password for Elasticsearch and Kibana and check once whether they are entered correctly and then click test and save.
9. On successful configuration click, the Next button to configure the Notification channel setup. Please refer the following link for setup Basic and Advanced Settings for reports
10. On successful Notification, channel configuration click the Create Report button to create a report.
Note: If you have changed the password in your Azure AD user, you should also change the password for the user in Skedler as well in order to avoid uninterrupted errors during report generation.