Tagged: , , ,

This topic contains 1 reply, has 2 voices, and was last updated by  Scott Heger 1 month, 3 weeks ago.

  • Author
    Posts
  • #22294
     eric.lawson 
    Participant

    In the Access Management documentation for 5.5 a single example is shown for adding applications to the dashboard:

    Add a Dashboard Class Name that identifies how the end user will access the app, such as SAML2ApplicationClass for a SAML v2.0 application. (https://backstage.forgerock.com/docs/am/5.5/maintenance-guide/#dashboard-setup)

    How can I create a new dashboard application for Oauth or OpenID applications?

    • This topic was modified 2 months ago by  eric.lawson.
    #22394
     Scott Heger 
    Participant

    It appears that the Dashboard Class Name doesn’t actually do anything. You can put “Foobar” in as the class name and fill out the rest of the fields as you would like. The behavior I see is that no matter what you put in for the class name all the dashboard service does is create an icon and a text link to the URL you define in the “Dashboard Login” field.

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.

©2018 ForgeRock - we provide an identity and access platform to secure every online relationship for the enterprise market, educational sector and even entire countries. Click to view our privacy policy and terms of use.

Log in with your credentials

Forgot your details?