<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
System Status
Announcements
Announcements
Search
Search
Select Language
Knowledge Base
Knowledge Articles
Support Videos ↗
Documentation
Product Documentation ↗
Developer Documentation ↗
Product Release Notes ↗
Community
Events & Webinars
Okta Ideas ↗
Resources
Product Hub
Customer Success Hub
Product Release Update
Learning
Okta Learning ↗
Get Support
Open a Case
HomeCommunityForum
0D50Z00008G7UhXSAVOkta Classic EngineLifecycle ManagementAnswered2025-03-10T09:02:44.000Z2016-03-14T17:26:54.000Z2017-06-29T02:04:09.000Z

b4vy3 (b4vy3) asked a question.

Edited by varun.kavoori1.5210444522562532E12 September 5, 2018 at 1:19 AM
Attribute Statements for AccelOps
We are trying to add an Attribute Statement for our AccelOps application, but AccelOps is not ingesting the new attribute.  Has anyone written an Attribute Statement to send email to AccepOps?

 

I have tried changing the Application username format to Email, but the Users are still being ingested with their Okta Usernames.

 

I currently have the following Attribute Statement configured:

email|${user.email}|urn:oasis:names:tc:SAML:2.0:attrname-format:uri
  • 2 answers
  • 676 views

  • svcV.75126 (Customer)

    Hi Nicholas,

     

    I am not sending any additional/custom attributes through to Accelops. I believe they are only looking at the nameid in the subject of the assertion.

     

    To change this value you would modify the application uesrname format from the Application->Sign On->Settings menu.

     

    I haven't seen the latest AO SAML documentation but that is how i have mine configured and it works fine. If you are trying to populate additional information for users in AO i don't know if their ACS does that, we use LDAP to populate the users but SAML for authentication.

     

    Hope that helps,

    -Matt

     

    Expand Post

  • b4vy3 (b4vy3)

    Thanks Matt,

     

    Did you have to do any special configuration in Okta or AO to authenticate to the LDAP accounts?  We had AO pull accounts from Okta to authenticate against.
This question is closed.
Loading
Attribute Statements for AccelOps