Skip to content
  • ZipCode Api
  • Blog
  • About RedLine13
RedLine13
Primary Navigation Menu
Menu
  • Start Testing
  • Demo
  • Pricing
  • Docs
    • Knowledge Base
    • AWS IAM Setup Instructions
    • Running a RedLine13 Load Test with Advanced Options
    • Scalability
    • Writing Open Load Tests in Your Language
    • Jenkins Plugin Setup
    • AWS Approval for Large Tests
    • Pro Features
  • JMeter
  • Partners

SAML Configuration with OKTA and RedLine13

By: RedLine13

Here are the step by step instructions for a SAML Configuration with OKTA and RedLine13. Read more about SAML SSO and RedLine13.

Login to OKTA.

Create a new app integration with SAML 2.0

Create a new app integration with SAML 2.0

Set General Settings
– Logo can be downloaded from LOGO

To Retrieve the Metadata document URL from OKTA you will need to create SAML integration with some temporary data.

  • SingleSignOn URL –  anything – (https://www.redline13.com/SSO/YOUR_DOMAIN)
  • Audience URL(SP Entity ID) – any string (will_change_after_setup)
  • Name ID Format – EmailAddress
  • In Attribute Statements add two attributes
    • givename – Type Basic,  user.firstName
    • surname – Type Basic, user.lastName
  • Hit Next 
To Retrieve the Metadata document URL from OKTA you will need to create SAML integration with some temporary data.

Complete Feedback for Internal app with Vendor

You should now land on the SAML settings page, copy the link address for Identity Provider Metadata 

  • You can either copy link address 
  • Or Download Identity Provider Metadata file 

Now we can switch from OKTA back to RedLine 13 and set up our SSO-SAML Connection

  • http://localhost/SSO/Manage [https://www.redline13.com/SSO/Manage]
  • Select SAML
  • Paste MetaData URL we copied from above 
    • If you downloaded file you can you use ‘Upload Metadata File’
  • Enter a domain name 
    • Recommendation – rl13-[yourcompany]
  • If your account does not have a team you will need to enter a name for a team.

Hit SAVE

And if everything worked out

OKTA and RedLine13

We now have to go back to our SAML provider (OKTA) and update a few fields to connect RedLine13 to your SAML SSO.  Go back to OKTA, find where you set up RedLine13.  In section general, to the right of SAML settings click ‘Edit’

Navigate to ‘Configure SAML’ either directly (if possible) or hitting ‘Next’

  • From Redline Copy “Reply URL (Assertion Consumer Service URL):” to “Single sign on URL” on OKTA.
  • From RedLine13 copy “Identifier (Entity ID)” to “Audience URI (SP Entity ID)” on OKTA.
  • On the OKTA screen scroll down and click Next (or Save). Make sure to hit Finish if using the OKTA wizard setup. 
OKTA and RedLine13

Now you can assign users and have them attempt to login.

2021-10-20
Previous Post: The Hitchhiking Guide to Load Testing Projects
Next Post: SAML Configuration with Azure AD and RedLine13

Recent Posts

  • Load Testing with AWS Spot vs On-Demand Instances – Spot Instances save you money
  • How many vCPUs needed for Load Testing?
  • Simple View of Security at RedLine13
  • Use Cases for the JMeter Dashboard Report
  • AWS Costs for Large JMeter Load Tests Run by Real Customers

Related

  • SAML SSO
  • SAML Configuration with OKTA and RedLine13
  • SAML Configuration with Azure AD and RedLine13
  • SAML Configuration with Google and RedLine13
  • RedLine13 Pricing and Features
  • RedLine13 Competitor Comparison
  • HTTP Archive and Google Big Query
  • General slow down for first byte across many sites
  • RedLine13, AWS, and other Cloud Platforms
  • TechStrong TV Interview with RedLine13 Co-Founder Bob Bickel Talks about Load Testing and DevOps

© RedLine13, LLC | Privacy Policy | Contract
Contact Us: info@redline13.com

Designed using Responsive Brix. Powered by WordPress.