Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Retrieving the token for the portal - user/generatessourl API call returns legacy portal URL

See original GitHub issue

Every bug report should have precise description and reproduction steps; console traces or source code references are appreciated.

For assistance requests, contact Azure support or submit a post on Stack Overflow. We don’t provide support through GitHub Issues. Feature requests can be raised on the Azure Feedback Forum.

Bug description

Generate SSO Url API still responds with a return url to the legacy developer portal.

Reproduction steps

  1. Enable the Management REST API
  2. Generate a SAS Token using these instructions:
  3. Call the generatessourl API using API version 2019-01-01 or 2018-06-01-preview
  4. The returned SSO url is generated using the legacy portal url ({service-name}

Expected behavior

An SSO url should be generated for the new developer portal url ({service-name}

Is your portal managed or self-hosted?


Release tag or commit SHA (if using self-hosted version)

API Management service name

Prefer not to say.


  • Operating system: Windows
  • Browser: Google Chrome
  • Version: 78.0.3904.97

Additional context

I would like to use the new developer portal with delegation but this always redirects me to the legacy portal everytime I get an SSO Url.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:14 (2 by maintainers)

github_iconTop GitHub Comments

joeystdiocommented, Nov 20, 2019

@ygrik isn’t this something that belongs in the documentation? I just ran into the same problem.

I think it’s a bit worrisome the new developer portal is no longer in preview while there is functionality missing/changed compared to the old (deprecated) developer portal. It is a paid product but the current experience in using it doesn’t give much confidence.

JCAMPOLPAcommented, Apr 30, 2020


Any news on this ? Having a SSO url for an already AzB2C signed user is a must-have !! We still have the error page with /signin-sso page

I think we miss guidance and doc on SSO, any update welcome.

Read more comments on GitHub >

github_iconTop Results From Across the Web

User - Generate Sso Url - REST API (Azure ...
Retrieves a redirection URL containing an authentication token for signing a given user into the developer portal.
Read more >
generateToken: Generate Token—ArcGIS REST APIs
This operation generates an access token in exchange for user credentials that can be used by clients when working with the Sharing API....
Read more >
Getting Started - GDC Docs - National Cancer Institute
The GDC API drives the GDC Data and Submission Portals and provides ... in the GDC Legacy Archive, add legacy to the endpoint...
Read more >
Authentication API
To complete the authentication process, make a call using the poll link to get session token and verify successful state. Request example for...
Read more >
HTTP - Developers - Dropbox
Use the refresh token to get a new access token. This request won't return a new refresh token since refresh tokens don't expire...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found