I have done some more analysis on this. I took the JWT tokens from the API calls 2 scenarios, one where we haven't overridden anything and kept everything as per the Framework, and one where we have our implementation.
I took those 2 JWT tokens and decoded them and came to know that the one which is using the default Framework implementation is these properties extra then the one where we have our implementation
session_id unique_name given_name email_verified phone_number_verified
Is there any significance of this? What I am thinking is somehow, it's because of the session id being null here.
I checked the current claims, there I am getting the preferred_username as "admin", which is correct. So, I am not sure if it's related to claims.
I am not sure, how this is specifically happening with the Payment packages. But for now I have commented all the line of code which is referencing the Payment packages. Can you pull the latest changes and try to build?
I have removed that package and pushed the changes, can you fetch the latest and try again?
Hi, we were able to finally implement what we required, as to use roles and permissions from the host tenant for all the other tenants. But, there is still a minor issue, in which we are getting the sessionId and the username of the logged in user as NULL in the currentUser section of the abp application configuration API call. It might get further issues in the application, can you suggest why would it happen and how do we resolve this?
Seems to be a package related issue, and we have this package (Volo.Payment.Domain) installed in the Saas service solution, can you build that first and then try to build other services one by one?
Can we please have a solution by today? It's a priority.
Any updates?
You can use the default angular app by ABP, that would work
Sure, here is the URL to the git repo that I have already created for the earlier ticket :
https://github.com/perquantum/g1-health/
Give me your git URL, so that I can add you as a contributor