Splunk, Auth0 and SAML SSO - part 2: Splunk configuration

In my previous blog post we have configured Auth0 as Identity Provider for Splunk using SAML protocol. Now it is time to configure Splunk. 

  1. As Splunk admin user, go to Settings / Authentication Methods. SAML is available as one of the external authentication methods. Select it.


  2. Click SAML Settings and the green button SAML configuration.


  3. Import IdP meta file. It is going to populate most of the fields for you. Still, there are a few settings that require manual adjustment.

    General Settings
    Entity ID: https://<your-splunk.com> - just enter your Splunk instance URL
    Advanced Settings
    Fully qualified domain name or IP of the load balancer: https://<your-splunk.com> - make sure this is correct; for instance you would like to have your FQDN here instead of container name
    Redirect port - load balancer port: 8000 - Splunk Web UI port

     
     

     
  4. You need to also set up aliases for SAML attributes containing realName, mail and role.
    Alias
    Role alias: http://schemas.auth0.com/rolez - or anything else you have set up; role is populated by JS rule we have added in Auth0 Auth Pipeline.
    RealName alias: http://schemas.auth0.com/nickname - "Name" property in Auth0 User Details.
    Mail alias: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress


  5. Wondering how I got these aliases? You can see your SAML token attributes via Auth0 dashboard: Applications / YourApp / Addons / SAML2 WEB APP / Settings / Debug button.


  6. Click Save button to finish SAML configuration. 
  7. The last step is to add group mappings. Click New Group button from the main SAML configuration dashboard in Splunk.


  8. Create the same groups you have added last time in Auth0 and assign Splunk roles to them. Done!


  9. Now you are going to be redirected to Auth0 when trying to access Splunk URL. You can test it by opening a new browser window in "Private mode".


  10. Congratulations! You are now logged in by SAML auth.


Comments

Post a Comment

Popular posts from this blog

Splunk: Authentication with Discord? Wht not! (OAuth 2.0)

Image
As some of you may already know, thanks to OAuth standard (which stands for Open Authorization) we don't need a separate account for every single website. It allows us to share information about our Google account with a third party, such as our name and e-mail address. On many sites we are free to use that "Login with Google/Facebook/other" button to sign up and/or login. Thanks to OAuth we don't have to give our password to the app/website. Upon login we are redirected to the OAuth provider site to login there (for instance to our Google account). And now the best part - if we are already logged on the provider site, this is likely to result in instant login on a third party site (sometimes interrupted by a pop up to confirm OAuth scope).  Here is a list of well-known OAuth providers (Wikipedia): https://en.wikipedia.org/wiki/List_of_OAuth_providers To get better understanding of OAuth 2.0 I would recommend reading these docs for developers: Using OAuth 2.0 to Acces
Read more

Study notes: Understanding DNSSEC

Image
DNSSEC Recently I have been researching materials covering DNSSEC as it is an important subject for LPIC-3 Exam 303. DNSSEC has been developed to address security issues of the DNS protocol, in particular preventing DNS cache poisoning attacks . Below I post DNSSEC description from Internet Corporation for Assigned Names and Numbers (ICANN), which I find useful and included in my study notes.  "DNSSEC strengthens authentication in DNS using digital signatures based on public key cryptography. With DNSSEC, it's not DNS queries and responses themselves that are cryptographically signed, but rather DNS data itself is signed by the owner of the data. Every DNS zone has a public/private key pair. The zone owner uses the zone's private key to sign DNS data in the zone and generate digital signatures over that data. As the name "private key" implies, this key material is kept secret by the zone owner. The zone's public key, however, is published in the zone itself
Read more

Linux: auditd fundamentals

Image
auditd stands for the audit daemon and it can be used to log events happening on a Linux host. It is a very powerful tool that can enable Threat Detection and/or - as the name suggests - create audit records. It writes to /var/log/audit/audit.log and collects such information as timestamp, PID, UID, Audit UID (auid), session info (ses), SELinux info (subj) and message (msg). Installation auditd is installed by default on most of the Linux distributions. In my case, I'm using RHEL 8 for the test purpose. The package is called audit .  Rules auditd is rule-based software and it support the following three types of rules: control : to configure general settings of the audit system, such as event rate limit, etc. file : file rules or watches can monitor files or directories and are using the following syntax: -w path-to-file -p permissions -k keyname syscall : these rules are loaded into the matching engine that intercepts every single syscall on the system and for this reason they
Read more