Activities of "gterdem"

Answer

You can check this community post about how to override login: https://community.abp.io/posts/how-to-customize-the-login-page-for-mvc-razor-page-applications-9a40f3cd

For LDAP, check out this sample: https://github.com/abpframework/abp-samples/tree/master/AbpLdapSample

You can open issue at OpenIdDict about it or keep using IdentityServer4 if it's working for you. This is not something we can implement.

Problem 2: See https://support.abp.io/QA/Questions/3461/missing-%27swaggeruiabpjs%27-in-WebGateway-api#answer-10db55b2-f8ac-5a22-3593-3a054638e7b2

Would you mind to mail to galip.erdem@volosoft.com so we can try to schedule an online meeting.

I couldn't reach your openid-configuration endpoint at 'https://appmicro-authserver/.well-known/openid-configuration'.

Can you check if the issuer is https://appmicro-authserver (HTTPS)?

If not, you can update your AuthServer with:

Configure<IdentityServerOptions>(options => { 
    options.IssuerUri = configuration["App:SelfUrl"]; 
});

and set both AuthServer and Blazor-Server AuthServer configuration in values.yaml file as:

authServer:
      authority: https://appmicro-authserver
      requireHttpsMetadata: "false"

Thanks for reporting.

We will fix this broken link as soon as possible.

I have refunded your credit.

The screenshot does not contain enough information to troubleshoot the problem.

Is this error from AuthServer or the blazor application? Can you also check the AuthServer logs? Trace the HTTP request please.

i did remove the https redirection in gateways modules and check auth modulle. everything fine now.

Changing the gatewayUr to l: https://appmicro-gateway-web/ (trailing slash at the end) and the auth server to https solved the mixed content error (Nr.3 above).. I can now authenticate succefull through swagger. Great

What do you think about my yaml files above for blazor. Blazor is still not accessible due error 500. How to solve that ?

What is the 500 error? If you have removed the midware it shouldn't be Volo.Abp.Http.Client.AbpRemoteCallException: An error occurred during the ABP remote HTTP request. (Connection refused (appmicro-gateway-web:443))

1- You don't need blazor-configmap.yaml since you won't be overriding any files.

You can update gatewayUrl: https://appmicro-gateway-web --> gatewayUrl: https://appmicro-gateway-web/ (trailing slash at the end). You can update authority: http://appmicro-authserver --> authority: https://appmicro-authserver (with https. And keep requireHttpsMetadata: "false")

2- You are trying to reach the gateway on SSL however it is not responding. High probably your gateway is running at port 80. This is related to the modification you did on 3rd step.

3- This HTTPS redirection is wrong. You shouldn't be redirecting incoming traffic to HTTPS. The modification you did for the gateways as in the post you shared is for auth server not gateways.

If you are using Blazor-Server, it is pretty similar to the MVC application configuration. You can use the web helm chart for Blazor-Server.

Is there any specific error you receive when using it?

We'll try to add Blazor-Wasm and Blazor-Server helm configurations in the 6.0 final version.

Showing 251 to 260 of 867 entries
Made with ❤️ on ABP v9.1.0-preview. Updated on November 11, 2024, 11:11