In this section you will configure one Auth0 tenant (tenant 2) to serve as an Identity Provider. You will do this by registering an application, but in this case, the ‘application’ you register is really a representation of tenant 1, the SAML Service Provider.
In the Auth0 dashboard:
Click on “Applications” link at left.
Click on the red “+ CREATE APPLICATION” button on the right.
In the Name field, enter a name (I’ve had mine as “Splunk 7.0.3 Container”).
Press the blue “SAVE” button.
Click on the “Settings” tab.
Scroll down and click on the “Show Advanced Settings” link.
In the expanded window, scroll down to the “Certificates” section and click on the “DOWNLOAD CERTIFICATE” link and select PEM from the dropdown, to download a PEM-formatted certificate. The certificate will be downloaded to a file called “YOUR_TENANT.pem”. Save this file as you will need to upload this file when configuring the other Auth0 tenant, tenant 1.
Click on the “Endpoints” tab and go to the “SAML” section.. Follow the “SAML Metadata URL” to download the IdP metadata file which we will need later in Splunk SAML configuration.
Click on the “Endpoints” tab and go to the “SAML” section. Copy the entire contents of the “SAML Protocol URL” field and save it as in the next step you will need to paste it into Splunk SSO configuration .
Creating User(s) in Auth0
Next, create a user to use in testing the SAML SSO sequence. In the Auth0 dashboard:
On the lefthand side, navigate to Users and Roles > Users
Click on the “+ CREATE YOUR FIRST USER” button.
In the Email field, enter an email for your test user. The domain name for the email should match what you enter in section 3 below. For example, if your user is firstname.lastname@example.org, you would enter that here, and then enter “abc-example.com” in step 3 below for the Email domain.
Enter a password for the user
For the Connection, leave it at the default value. (Username-Password-Authentication)
Press the blue “SAVE” button.
Creating Roles and assigning user(s) in Auth0
Since Splunk relies on the IdP to return the user roles you will need to create at least one new Role and assign a user to it.
On the lefthand side, navigate to Users and Roles > Roles
Click on the “+ CREATE ROLE” button.
Once the Role is created click on “ADD USERS” button
From the dropdown list select the user and click “ASSIGN“
Navigate to “Settings” > “Access Controls” > “Authentication Method”
Under External authentication methods, select “SAML” and click the “SAML Settings” link
Create the required SAML groups (and assign roles to them), so that these group names will be matched with the Auth0 role names
On top right corner click the “SAML Configuration” button
On the right of the “Metadata XML File” click “Select File” and upload the IdP metadata file that you’ve downloaded from Auth, it will be called something like dev-1a2b3c4d-idp_au_auth0_com-metadata.xml (the first part will depend on your Auth0 t
Configure Splunk SSO with Auth0 as your identity provider was last modified: June 4th, 2019 by Ilya Reshetnikov
I wanted to play with SAML Authentication in Splunk and decided to use Auth0 is my SAML Identity Provider (IdP).
Since i’ve never worked with Auth0 I just followed the SAML SSO with Auth0 as Service Provider and as an Identity Provider tutorial,, which worked well, but when I tried to use Splunk as Service Provider(SP), i.e. SAML service consumer, I noticed that roles are not returned by Auth0 SAML assertion, so I had to find a way to return user roles in Auth0 together with other user’s information.
Of course the prerequisite of returning roles assigned to the user is to have them defined, so configure a few Roles under the User & Roles section on the left and assign 1 or more rule to a user.
I’ve created bu1_p and bu2_p (as for Business Unit 1/2 – Power User).
Next you will need to configure a Rule.
So from different sources I’ve stitched up a simple rule that adds roles assigned to a user and adds them to the user context.
Go to Rules and create a new Rule using empty rule template
Update the function to look like this:
Add Roles to User Rule
// Get the user roles from the Authorization context
I’ve started working with Splunk KV store for one of my recent projects. It is a robust system with an extensive API. since I was learning and documenting my fundings anyway I thought, why not put up a blog post about how to manage Splunk KV Store using REST API.
Sometimes you want to have a certain colour for the Google Calendar events. I know that you can do it manually, but what if you want it to be colour coded automatically based on some filters. In my case it was based on meeting organizer (my wife to be precise 🙂 ). So decided to try and colour code Google calendar events automatically using Google Apps Script.
Here is how to verify ownership of a site for bing in Google Domains
There are 3 options
Option 1: Place an XML file on your web server
Option 2: Copy and paste a
tag in your default webpage
Option 3: Add CNAME record to DNS
I chose option 3 (and it is the focus of this post) when I was verifying my ALinks4U.com domain for 2 reasons: (1) It doesn’t require to touch you website code and/or have access to your site’s filesystem (2) It is unique to Google Domains (vs other hosting platforms)
Verify ownership of a site for bing in Google Domains
Under Custom resource records add a new CNAME record
Back in the Bing Webmaster Console hit the Verify button. Please note that it might take some time for the DNS resolution to start working (took about 10 minutes for me)
That’s it, now your new site is verified by Bing and will be crawled and indexed and will appear in relevant search results. As an additional benefit, sites that are crawled by Bing are also indexed by DuckDuckGo.com
Verify ownership of a site for Bing in Google Domains was last modified: October 20th, 2018 by Ilya Reshetnikov