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. https://docs.microsoft.com/en-us/rest/api/apimanagement/2019-01-01/user/generatessourl

Reproduction steps

Enable the Management REST API
Generate a SAS Token using these instructions: https://docs.microsoft.com/en-us/rest/api/apimanagement/apimanagementrest/azure-api-management-rest-api-authentication
Call the generatessourl API using API version 2019-01-01 or 2018-06-01-preview
The returned SSO url is generated using the legacy portal url ({service-name}.portal.azure-api.net)

Expected behavior

An SSO url should be generated for the new developer portal url ({service-name}.developer.azure-api.net).

Is your portal managed or self-hosted?

Managed

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

API Management service name

Prefer not to say.

Environment

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:
Created 4 years ago
Comments:14 (2 by maintainers)

Top GitHub Comments

1reaction

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.

0reactions

JCAMPOLPAcommented, Apr 30, 2020

Hello

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.