Comments (8)
Can I have some response please!
from active-directory-b2c-dotnetcore-webapp.
@parakhj yet again no response from anyone in your team
from active-directory-b2c-dotnetcore-webapp.
Apologies @phatcher. The URL's, while different, do the same thing. Some OIDC libraries don't like the fact that there is a non-standard parameter (the p parameter for policy), so we have to provide a URL format that has the policy in the path.
For quicker replies, I encourage also posting on stackoverflow, using the tag 'azure-ad-b2c'. There are a lot more people monitoring that
from active-directory-b2c-dotnetcore-webapp.
@parakhj No if you are going to post examples here, it makes sense to support them here. Also the only question posted on SO regarding this example has no replies apart from the author.
If you are not going to support these examples directly, make it clear in the documentation page of the project.
What's not clear from the documentation is that from the .NET to the dotnetcore version you must change the reply url in the Azure B2C tenant to include "signin-oidc" i.e. if you previously had "https://localhost:44316" you must also add "https://localhost:44316/signin-oidc" for the dotnetcore client code to work
from active-directory-b2c-dotnetcore-webapp.
The redirect URL is something you have full control over. It's just a matter of what URL the application is listening at. The .dotnetcore convention is to add the code that listens to the reply behind the path specified by /signin-oidc at the end. However, your code could handle it at the root level as well. It's just how you implement it
from active-directory-b2c-dotnetcore-webapp.
@parakhj From what I can see yes we do have full control over the reply url, however we must append /signin-oidc to the registered url in the Azure B2C tenant, or whatever string is assigned to OpenIdConnectOptions.CallbackPath, which won't except an empty string.
So from my perspective, this is a breaking change since I didn't have to do this for the standard .NET WebApp code and you have failed to adequately document this - I say this because there are about four open issues here which are all about this problem.
When you say "your code could handle it at the root level", can you explain what you mean by this?
from active-directory-b2c-dotnetcore-webapp.
Ah okay. Thanks for clarifying that - didn't properly acknowledge that you are migrating from your .NET webapp code.
Sure I'll work on making the instructions more clear.
from active-directory-b2c-dotnetcore-webapp.
Closing this issue as this sample is being archived and replaced by a newer ASP.NET Core 3.1 sample.
See Readme.md
from active-directory-b2c-dotnetcore-webapp.
Related Issues (20)
- got secure error when I try to sign in HOT 2
- Not compatible with aspnet core 2.1 HOT 1
- Error from RemoteAuthentication: Message contains error: 'redirect_uri_mismatch', error_description: 'AADB2C90006: The redirect URI 'http://b2.95e4700435c54427a457.northeurope.aksapp.io/signin-oidc' provided in the request is not registered for the client id 'eb201049-e7b1-4227-9a7c-5bb259261d37'. Correlation ID: 8f75359e-009f-44e3-b537-3f85f58cdd9c HOT 6
- User.Identity.Name is null and HttpContext.User.Claims is empty HOT 6
- ERROR Account username: Missing from the token response environment login.microsoftonline.com home account id: AccountId: XXXX HOT 8
- Single-Sign Out AD B2C HOT 2
- NullReferenceException in MSALSessionCache constructor HOT 1
- acquireTokenSilent sometimes returns a null accesstoken HOT 1
- Error messages in OnRemoteFailure should be url encoded before appending to query string HOT 3
- Latest version of AAD B2C? HOT 2
- Update the repository to not use Bower HOT 3
- Update the repository to use the latest MSAL version HOT 2
- b2clogin.com for ASP.NET Core HOT 7
- No accounts being returned on cca.GetAccountsAsync()
- Words 'simple' and 'dead simple' should be removed from content. HOT 1
- Unit testing for SessionController HOT 1
- Compatibility with .NET Core 3.1 HOT 2
- How do I diagnose errors? HOT 1
- How to pass domain_hint while calling B2C for login HOT 1
- How to select a policy at runtime?
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from active-directory-b2c-dotnetcore-webapp.