Activities of "okains"

All Question Answer
Newest Oldest
Admin user menu not showing on tiered app in dev / production, and logged in with same menu issue but not authenticated in production Azure deployment slots. #7716
Answer

Ok, just emailed them to you, thanks.

Admin user menu not showing on tiered app in dev / production, and logged in with same menu issue but not authenticated in production Azure deployment slots. #7716
Answer

Hi,

I noticed something just now, I had a mistake in the config. I had shifted this entire app to InteractiveServer, however I left 1 setting at InteractiveAuto by mistake!

I have fixed that issue and redeployed and it seems to have fixed the 404 page flash that was happening. However the initial issues are still there:

Admin user menu not showing on tiered app in dev / production, and logged in with same menu issue but not authenticated in production Azure deployment slots. #7716
Answer

Also just emailed the EnvVars dumps from Kudu...

Admin user menu not showing on tiered app in dev / production, and logged in with same menu issue but not authenticated in production Azure deployment slots. #7716
Answer

Hi,

OK I just emailed you the full logs.txt files for both services.

The appsettings.json config should be overridden by the AppService Environment Variables config, I had sent that config to you in the previous email.

I can send a full Environment Dump from Kudu if you think that will help?

Thanks,

Karim

Admin user menu not showing on tiered app in dev / production, and logged in with same menu issue but not authenticated in production Azure deployment slots. #7716
Answer

Hi,

Logs and configuration all sent to your email address.

Thanks

Admin user menu not showing on tiered app in dev / production, and logged in with same menu issue but not authenticated in production Azure deployment slots. #7716
Answer

Hi,

I have sent those details to your email address.

Thanks,

Karim

Admin user menu not showing on tiered app in dev / production, and logged in with same menu issue but not authenticated in production Azure deployment slots. #7716
Question
  • ABP Framework version: v8.2
  • UI Type: Blazor Server
  • Database System: EF Core (SQL Server)
  • Tiered (for MVC) or Auth Server Separated (for Angular): yes
  • Exception message and full stack trace:
  • Steps to reproduce the issue:

I am working through a CI / CD implementation using Azure Deployment slots. I have a tiered application that I am trying to get deployed correctly. This is just a basic, no changes, out of the box 3 tier application generated by ABPSuite that I use as a base dev environment for testing.

First problem is that I can not see the full menu for the admin user in the tiered app on neither dev nor production. However in dev everything works as expected, I can create users, and I am authenticated as admin ( it seems ).

For reference, I created a single tier app, and I see the admin user menu as I would expect:

So I would expect to see this menu in my tiered app. They were created exactly the same time, same 8.2 version number, no code updates, just out of the box ABP. But I do not get the user / admin menu in my fresh and clean 3 tier app.

The real issue here is when I deploy a 3 tier app using Azure Deployment Slots to a staging environment on Azure. I can log in OK, and I get the same no options Admin menu as I got in my local dev environment:

However I can’t see any admin menu, and I get an Unauthorized exception after trying to do anything. Even though I seem to be logged in as the admin user.

After Refresh:

This to me seems like a configuration issue, but I can not seem to see any difference in config between environments.

Any insight would be much appreciated.

Thanks,

Karim Ainsworth

Can't generate long lived auth tokens after 8.2 upgrade #7626
Answer

OK I think this might have worked, I set my clock to 2026, got a 401 as expected. Set it to October ( + 2 Months ) and got a 200.

I will fix this now on my production Azure environment and let's see if the token works as expected.

I will close this ticket after a couple of days as long as the token is still alive.

Thanks for your help!

Can't generate long lived auth tokens after 8.2 upgrade #7626
Answer

OK, i have logged out / logged back in as admin to the auth server, I can see the sessions now. I don't see an active Session for the token that I generated last night.

Are you saying that because now I have logged in, that if I create a new token, that it won't expire? I can try that now and see how it works. Here is the current Sessions without the new token :

New token generated, getting back a 200 with data:

And I can see the new token now here:

So this all looks good, are you saying that now this token will honor it's expiration date properly?

I suppose now we just wait and see if it is still valid after 1 day then yeah?

Thanks,

Karim

Can't generate long lived auth tokens after 8.2 upgrade #7626
Answer

Hi,

I am getting a 404 on account/sessions, also account/session, and I tried to find it in the settings / admin menus but can't find, is that the right URL?

Also, the token I generated last night is now giving me a 401:

And here are the logs after making that API call:

https://drive.google.com/file/d/1BeYcZz4k9WFmyTGTBI8vH4SeehbsnonI/view?usp=sharing

This time we didn't get 24 hours, was working 14 hours ago. I don't see anything obvious in the logs.

I just paused for a bit, then tried hitting the API endpoint again, of course got a 401, but not much additional in the logs, that was done at 13:38:

2024-08-06 13:17:51.296 +06:30 [DBG] The event OpenIddict.Server.OpenIddictServerEvents+ApplyIntrospectionResponseContext was successfully processed by OpenIddict.Server.AspNetCore.OpenIddictServerAspNetCoreHandlers+ProcessJsonResponse1[[OpenIddict.Server.OpenIddictServerEvents+ApplyIntrospectionResponseContext, OpenIddict.Server, Version=5.5.0.0, Culture=neutral, PublicKeyToken=35a561290d20de2f]]. 2024-08-06 13:17:51.296 +06:30 [DBG] The event OpenIddict.Server.OpenIddictServerEvents+ApplyIntrospectionResponseContext was marked as handled by OpenIddict.Server.AspNetCore.OpenIddictServerAspNetCoreHandlers+ProcessJsonResponse1[[OpenIddict.Server.OpenIddictServerEvents+ApplyIntrospectionResponseContext, OpenIddict.Server, Version=5.5.0.0, Culture=neutral, PublicKeyToken=35a561290d20de2f]]. 2024-08-06 13:17:51.296 +06:30 [DBG] The event OpenIddict.Server.OpenIddictServerEvents+ProcessRequestContext was successfully processed by OpenIddict.Server.OpenIddictServerHandlers+Introspection+ApplyIntrospectionResponse1[[OpenIddict.Server.OpenIddictServerEvents+ProcessRequestContext, OpenIddict.Server, Version=5.5.0.0, Culture=neutral, PublicKeyToken=35a561290d20de2f]]. 2024-08-06 13:17:51.296 +06:30 [DBG] The event OpenIddict.Server.OpenIddictServerEvents+ProcessRequestContext was marked as handled by OpenIddict.Server.OpenIddictServerHandlers+Introspection+ApplyIntrospectionResponse1[[OpenIddict.Server.OpenIddictServerEvents+ProcessRequestContext, OpenIddict.Server, Version=5.5.0.0, Culture=neutral, PublicKeyToken=35a561290d20de2f]]. 2024-08-06 13:17:51.296 +06:30 [INF] Request finished HTTP/1.1 POST https://localhost:44359/connect/introspect - 200 348 application/json;charset=UTF-8 26.4754ms 2024-08-06 13:38:11.132 +06:30 [INF] Lock is acquired for TokenCleanupBackgroundWorker 2024-08-06 13:38:11.133 +06:30 [INF] Lock is acquired for IdentitySessionCleanupBackgroundWorker 2024-08-06 13:38:11.139 +06:30 [INF] Start cleanup. 2024-08-06 13:38:11.140 +06:30 [INF] Start cleanup tokens. 2024-08-06 13:38:11.144 +06:30 [INF] Start cleanup sessions. 2024-08-06 13:38:11.198 +06:30 [INF] Cleanup sessions completed. 2024-08-06 13:38:11.198 +06:30 [INF] Lock is released for IdentitySessionCleanupBackgroundWorker 2024-08-06 13:38:11.206 +06:30 [INF] Start cleanup authorizations. 2024-08-06 13:38:11.251 +06:30 [INF] Lock is released for TokenCleanupBackgroundWorker

Thanks,

Karim

Showing 41 to 50 of 134 entries
Made with ❤️ on ABP v9.0.0-preview Updated on September 20, 2024, 05:21