API Authentication Update - SAML


I am unable to log in to the Reporting API when SAML authentication is enabled.


This is because the Reporting API login page does not currently support SAML authentication, which prevents any administrative functions from being executed (i.e. tenant creation/update/delete, tuning tag creation/update/delete) 

Workaround Steps

A workaround to change the Reporting API login page to one that supports SAML authentication via an nginx configuration change. Please perform the steps below:

  1. SSH to the REPORTING NODE as the Interset User
  2. Type in the following command to navigate to the nginx configuration (/etc/nginx/conf.d/) directory:
    • cd /etc/nginx/conf.d
  3. Type in the following command to edit the interset.conf:
    • sudo vi interset.conf
  4. Locate the following section:
    location ~ ^/endpoint/reports/(?<redir>.*)$ {
    proxy_http_version 1.1;
    keepalive_requests 0;
  5. Once the section above is located, add the following section below it:
    location /login {
    if ($arg_redirect_uri) {
    return 301 $scheme://$host/login?external=$arg_redirect_uri;
    rewrite ^ /dashboard/login$1;
  6. Save the changes, and exit the file
  7. Type in the following command to restart nginx:
    • For EL6:
      • sudo service nginx restart
    • For EL7:
      • sudo systemctl restart nginx
  8. Open up a web browser and navigate to the Reporting API URL:
  9. On the Swagger page, click the Authorize button (top of webpage)
  10. In the pop up, click Authorize.
  11. The login page will then redirect to the SAML assertion page.
  12. Please authenticate with a valid SAML account and its respective credential.
    • NOTE: Please ensure that the account that is being authenticated is in the Interset adm.
  13. Click Sign In.
  14. If the authentication is successful, access to swagger will then be granted.

Applies To

  • Interset 5.4.x or higher
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request