openiddict-core: token enpoint started to return 404
So trying the with invalid credentials and i get all the good error codes, but submitting good credentials IIS return 404 right after the seclect application. Strange thing is that it worked like a charm
Microsoft.AspNetCore.Hosting.Internal.WebHost:Information: Request starting HTTP/1.1 POST http://localhost:3174/connect2/token application/x-www-form-urlencoded 83
Microsoft.EntityFrameworkCore.Storage.Internal.RelationalCommandBuilderFactory:Information: Executed DbCommand (9ms) [Parameters=[@__identifier_0='?' (Size = 450)], CommandType='Text', CommandTimeout='30']
SELECT TOP(2) [application].[Id], [application].[ClientId], [application].[ClientSecret], [application].[DisplayName], [application].[LogoutRedirectUri], [application].[RedirectUri], [application].[Type]
FROM [OpenIddictApplications] AS [application]
WHERE [application].[ClientId] = @__identifier_0
Microsoft.AspNetCore.Hosting.Internal.WebHost:Information: Request finished in 71.801ms 404
To be honest i probably f***ed up something since it did work, but i have no idea after an hour of look in to this. Let me know if you can help and you need any more info.
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Reactions: 3
- Comments: 24 (9 by maintainers)
Sure. If you don’t, the authorization endpoint won’t be enabled.
@t3hmun thanks for the tip. For clarity, I removed the abbreviated sample from the README: https://github.com/openiddict/openiddict-core/commit/44ee0f6ceaf21936b7f938e026ed0889bf1b5374
The “complete” sample has the right check: https://github.com/openiddict/openiddict-core/blob/dev/samples/Mvc.Server/Controllers/AuthorizationController.cs#L124-L130
Nope, that’s a deliberate design change introduced in the last version. As explained in the README, you must know provide your own token endpoint action to handle token requests.