Posts made by mark.robustelli

@david-cuen OK, I was able to get more than 10, but you're right about it possibly being the size. Is it possible for you to share the theme you are using with us or me individually? I don't want you to give away any secrets, proprietary info or share anything private if you can't but getting a look at the theme may help.

@bernardo-munz Did you play with the SameSite setting?

@david-cuen Awesome that you have isolated the issues. I am going to test from my side and see if I can replicate with the 10+ themes. If I can then you should report this as a bug. I will let you know what I find. Hope to be able to get to this today.

@david-cuen can you try to spin up a new instance and let me know if you see the problem? If not, it may have to do specifically with the themes themselves. If the new instance works correctly, import each theme and test. This may help narrow the issue.

@david-cuen Thanks for the detailed message. I hope to have some time today to try and replicate this. I will let you know what I see.

@simon-chrzanowski can you please share the code you using? (please be sure to hide anything sensitive like your API Key)

@alexandros-nafas , were you able to figure it out?

@alexandros-nafas are you trying to make an update through the API then reflect that value of are you trying to pass a value in the URL and get that? It may help to give an example.

@johnmiller It looks like the issue is that the 'retrieve a user via JWT' functionality was removed in 1.60.0. (It appears the User API JWT authentication method was deprecated in version 1.50.0. An issue has been filed to remove it from the client libraries.

Thank you from bringing this to light.

@rachel-flatt OK, it looks like your application is using the JWT setttings from the Tenant. You can go to the Admin UI select Tenants -> Find the tenant your application is under -> Select Edit and go to the JWT tab. You should find the settings there.

@johnmiller Can you please share a code snippet of the call? I will try to recreate and see if we can figure something things out.

@Ruka , this seems like something that should be reported as an issue.

@patrick_ag Is this just when you are loading the page or are you trying to take some action?

@rachel-flatt It is odd that you do not see the page. Are you an admin user? Can you post a screenshot with what you do see? (Please be sure to redact secrets and private information)

@oliver-muthusami hmmm. I did some poking around Microsoft's documentation and found this.

The inclusion of the refresh token in the response can depend on several factors, including the specific configuration of your application and the scopes requested during the authorization process. If you expect to receive a refresh token in the response but fail to, consider the following factors:

Scope requirements: Ensure that you're requesting the offline_access scopes along with any other necessary scopes.
Authorization grant type: The refresh token is provided when using the authorization code grant type. If your flow differs, the response can be affected.
Client configuration: Check your application's settings in the identity platform. Certain configurations may restrict the issuance of refresh_tokens.

Are you sure you have Entra configured correctly?

@oliver-muthusami Awesome that you got what you need. Thanks for reaching out and letting us know!

@dalamenona This error is coming from Prometheus right? Is there a way to get it to tell you which metric is being reported? If not, could you set up a network monitor and capture the traffic that is being sent to narrow down the metric being sent by FusionAuth that is causing the problem? Maybe then we can look into why FusionAuth is sending the conflicting data.

@oliver-muthusami Have you looked at what Entra ID returns in the reconcile lambda?

@dalamenona I see your point about the Database_primary_pool_MaxConnections being set to 20 on the value for usage being reported above that. Browsing around the web, I came across something that said Database_primary_pool_Usage is over the lifetime of the application, but can't seem to find the source now. You also make a valid point about around the other data defenitions. It may make sense to do a deeper dive into HikariCP sources in general. There may be some answers there.

Anyone here familiar with these numbers?

It may also make sense for you to open an issue with FusionAuth as it is not clear to me if these numbers are coming from FusionAuth or HikariCP.