Sorry if this isn't the right spot to ask; Feel free to point me in the right direction.

I've been reading the docs, and I've been unable to find how a user is given access to a specific application. If each application has their own connection, how are users connected between the applications?

On the client level we should add a new checkbox "Allow custom URLs". If this checkbox is enabled, a new field will show up, "Custom URL". In this field a customer will enter a custom URL where we should redirect to, eg:

https://github.com/auth0
https://myapp.com/sso?connection={connection}

If this option is enabled we should simply redirect to this url instead of generating the default /authorize url. The url should support variables, where we might need to replace:

• connection
• client_id
• domain
• callback

Hi, I followed the instructions here to set up a new SSO Dashboard, but it hasn't worked for me.

1. The URL in the docs (below) sees to be different to what the Extensions page is pointed at
   

If I go to the Installed Extensions page in my Auth0 portal, the SSO Dashboard extension points to this URL instead: https://dev-theburningmonk-ec.us.webtask.run/auth0-sso-dashboard/admins/login

and I assume the user login page would be at:
https://dev-theburningmonk-ec.us.webtask.run/auth0-sso-dashboard/login

2. If I visit the user login page I see this:
   
   even though I had followed the instructions and added both user and admin URLs to the allowed callback URLs:
   

3. If I visit the admin login page then the Auth0 login page pops up, but when I enter my username and password to sign in I get a validation error
   

So, so far I've only managed to access the SSO dashboard from the Extensions page by clicking on the SSO Dashboard extension from the Installed Extensions page.

It feels like maybe I might have misconfigured something along the way, but I've followed the instructions step-by-step twice and have got the same result, so maybe the docs are out of date?

Any help would be much appreciated!

Does this dashboard currently support, or have plans to support hiding applications that a user doesn't have access to?

Hi,
great extension to Auth0 - I managed to create a dashboard for my client of apps that require auth0 login.
Is it possible to localize into other languages, so instead of english I could have polish - at least for end-users ?

npm install -> old dependencies
npm run serve:dev -> not found

Any chance to see this fixed?

When logging out as an end user, it should use AUTH0_DOMAIN. But an admin logging out, should use AUTH0_RTA.

For SSO integrations we can already fill in:

1. The protocol
2. The logo url
3. The name
4. The callback url

When creating a new application, pick the first callback url by default.

By default applications should be ordered by name, but in addition to that, we should support:

• Order as a setting on the application
• Allow end users to order applications for themselves (and store the order in webtask storage or app_metadata)
• Allow end users to "pin" applications on top if there are too many apps

Hide applications that you don't have access to by filtering based on group/role

I tried sso dashboard extension and try to configure role base access controling using authorization extension.

I found this PR, so I understand disabled authz integration by default. But, I could not find to how to enable integrated with auth'z extension.

How can I enable authz extension integration? or where is the document?

I want to add links for G Suite Apps to the SSO Dashboard. These are not individually setup within Auth0 as Auth0 is setup as the IDP for Google Apps.

I want to add the link for gmail into the SSO Dashboard and then the Service provider login initiates the SSO with the IDP( Auth0) because Auth0 is setup as an IDP for google apps.

Currently I can not do this as I have to define everything related to Auth0 client when defining an application within SSO dashboard. Also G Suite does not support IDP Initiated SSO as it requires a RelayState being passed from the SP to the IDP.

When the connection parameter is specified in the New Application form, it incorrectly gets encoded as & to login url instead of ? which fails the SAML login

Broken URL: https://{domain}.auth0.com/samlp/HbOLz0nYYKCwR0sjBf2MoUo2w5jaAGnI&connection=db

Working URL: https://internalserver.auth0.com/samlp/HbOLz0nYYKCwR0sjBf2MoUo2w5jaAGnI?connection=db