Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The sample encountered a problem #706

Closed
qq1176914912 opened this issue Mar 5, 2024 · 6 comments
Closed

The sample encountered a problem #706

qq1176914912 opened this issue Mar 5, 2024 · 6 comments
Assignees
Labels
bug Something isn't working

Comments

@qq1176914912
Copy link

Hello.
(CIBA) Example After receiving the verification address, enter this address and click Confirm. An error occurs:
image
5001 Error:
image
I remember there was no problem before, I don't know why now, all the certificates have not expired.

@simpleidserver
Copy link
Owner

This issue will be fixed in the ticket #687

@simpleidserver simpleidserver self-assigned this Mar 8, 2024
@simpleidserver simpleidserver added the duplicate This issue or pull request already exists label Mar 8, 2024
@simpleidserver
Copy link
Owner

This issue is fixed in the master branch :)

@simpleidserver simpleidserver moved this from In Progress to Done in @simpleidserver's Release 4.0.8 Mar 8, 2024
@qq1176914912
Copy link
Author

This issue is fixed in the master branch :)

1、I tested the ciba project, and I found that when I logged in with the account declared in the ciba project, the 5001 address reported an error:
image

Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware[1]
An unhandled exception has occurred while executing the request.
System.Reflection.TargetException: Non-static method requires a target.
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Reflection.PropertyInfo.GetValue(Object obj)
at SimpleIdServer.IdServer.Extractors.PropertyClaimExtractor.Extract(HandlerContext context, IClaimMappingRule mappingRule) in D:\Aila\FW-IAM-Casbin\src\IdServer\SimpleIdServer.IdServer\Extractors\PropertyClaimExtractor.cs:line 26
at SimpleIdServer.IdServer.Extractors.ClaimsExtractor.Extract(HandlerContext context, IEnumerable1 mappingRules) in D:\Aila\FW-IAM-Casbin\src\IdServer\SimpleIdServer.IdServer\Extractors\ClaimsExtractor.cs:line 54 at SimpleIdServer.IdServer.Extractors.ClaimsExtractor.ResolveGroupsAndExtract(HandlerContext context, IEnumerable1 mappingRules) in D:\Aila\FW-IAM-Casbin\src\IdServer\SimpleIdServer.IdServer\Extractors\ClaimsExtractor.cs:line 45
at SimpleIdServer.IdServer.Api.Token.TokenBuilders.AccessTokenBuilder.Build(BuildTokenParameter parameter, HandlerContext handlerContext, CancellationToken cancellationToken, Boolean useOriginalRequest) in D:\Aila\FW-IAM-Casbin\src\IdServer\SimpleIdServer.IdServer\Api\Token\TokenBuilders\AccessTokenBuilder.cs:line 49
at SimpleIdServer.IdServer.Api.Token.Handlers.CIBAHandler.Handle(HandlerContext context, CancellationToken cancellationToken) in D:\Aila\FW-IAM-Casbin\src\IdServer\SimpleIdServer.IdServer\Api\Token\Handlers\CIBAHandler.cs:line 75
at SimpleIdServer.IdServer.Api.Token.Handlers.CIBAHandler.Handle(HandlerContext context, CancellationToken cancellationToken) in D:\Aila\FW-IAM-Casbin\src\IdServer\SimpleIdServer.IdServer\Api\Token\Handlers\CIBAHandler.cs:line 123
at SimpleIdServer.IdServer.Api.Token.TokenController.Post(String prefix, TokenRequest request, CancellationToken token) in D:\Aila\FW-IAM-Casbin\src\IdServer\SimpleIdServer.IdServer\Api\Token\TokenController.cs:line 46
at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.TaskOfIActionResultExecutor.Execute(ActionContext actionContext, IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.g__Awaited|12_0(ControllerActionInvoker invoker, ValueTask`1 actionResultValueTask)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.g__Awaited|10_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()
--- End of stack trace from previous location ---
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.g__Awaited|25_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResourceExecutedContextSealed context)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeFilterPipelineAsync()
--- End of stack trace from previous location ---
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.g__Logged|17_1(ResourceInvoker invoker)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.g__Logged|17_1(ResourceInvoker invoker)
at Microsoft.AspNetCore.Routing.EndpointMiddleware.g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger)
at SimpleIdServer.IdServer.Swagger.SidSwaggerUIMiddleware.Invoke(HttpContext httpContext) in D:\Aila\FW-IAM-Casbin\src\IdServer\SimpleIdServer.IdServer.Swagger\SIDSwaggerUIMiddleware.cs:line 81
at SimpleIdServer.IdServer.Swagger.SIDSwaggerMiddleware.Invoke(HttpContext httpContext, ISwaggerProvider swaggerProvider) in D:\Aila\FW-IAM-Casbin\src\IdServer\SimpleIdServer.IdServer.Swagger\SIDSwaggerMiddleware.cs:line 37
at SimpleIdServer.IdServer.Middlewares.MtlsAuthenticationMiddleware.InvokeAsync(HttpContext context) in D:\Aila\FW-IAM-Casbin\src\IdServer\SimpleIdServer.IdServer\Middlewares\MtlsAuthenticationMiddleware.cs:line 44
at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
at SimpleIdServer.IdServer.Middlewares.LanguageMiddleware.InvokeAsync(HttpContext context) in D:\Aila\FW-IAM-Casbin\src\IdServer\SimpleIdServer.IdServer\Middlewares\LanguageMiddleware.cs:line 28
at SimpleIdServer.IdServer.Middlewares.RealmMiddleware.InvokeAsync(HttpContext context) in D:\Aila\FW-IAM-Casbin\src\IdServer\SimpleIdServer.IdServer\Middlewares\RealmMiddleware.cs:line 62
at Microsoft.AspNetCore.Localization.RequestLocalizationMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddlewareImpl.Invoke(HttpContext context)

2、The previous problem appears again: even if I do not apply the account set in ciba, the authorization can still be successful, and "The consent is confirmed" is displayed.
#686 (comment)

@qq1176914912
Copy link
Author

I saw that you completed "gotify", I tried to use ciba to test, I changed the notification method of the account used by ciba to "gotify" :
image
When I started ciba I found that there was no message in gotify:
image
According to the official document "(https://gotify.net/docs/pushmsg)" push message needs address, port, token and message, but I see that your configuration for "gotify" only has the address account password, so how to use this thing?
And if you create a process for "gotify" in ACR, when you click on it, the page is blank.
image

@simpleidserver
Copy link
Owner

CIBA Confirmation by Any User

Security has been re-enabled in the BC Channel authorization endpoint.

Gotify

The goal of the Gotify notification method is to replace Firebase for receiving CIBA notifications directly in the mobile application. With this method, you can enroll the mobile application without using Firebase.

It's normal that messages are not pushed to Gotify if your user hasn't enrolled their mobile application. We will create a tutorial (Ticket #711) to explain how to enroll a mobile application with Gotify in SimpleIdServer.

In the ACRS view, we removed all PUSH methods such as Gotify and Firebase.

Unable to Retrieve Claims (Exception)

This issue is also fixed in the master branch.

@simpleidserver simpleidserver added bug Something isn't working and removed duplicate This issue or pull request already exists labels Mar 11, 2024
@qq1176914912
Copy link
Author

CIBA Confirmation by Any User

Security has been re-enabled in the BC Channel authorization endpoint.

Gotify

The goal of the Gotify notification method is to replace Firebase for receiving CIBA notifications directly in the mobile application. With this method, you can enroll the mobile application without using Firebase.

It's normal that messages are not pushed to Gotify if your user hasn't enrolled their mobile application. We will create a tutorial (Ticket #711) to explain how to enroll a mobile application with Gotify in SimpleIdServer.

In the ACRS view, we removed all PUSH methods such as Gotify and Firebase.

Unable to Retrieve Claims (Exception)

This issue is also fixed in the master branch.

The problem has been resolved, thank you for your modification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
No open projects
Development

No branches or pull requests

2 participants