Hi Support Team,
I would like to ask if there is a way to hide away "Junior" & "Senior" in the "User" => "Edit" popup as below: If there is any, could you show me how this could be achieved?
Hope to hearing from you guys soon.
Thanks.
Hi, it's been a while. When will I get the answer for this?
Hello, is there any update on this?
Hi Support Team,
I have a requirement to hide/show certain pages based on current user role. So I came up with the idea to inject User Service
into route.provider.ts
, it looks like this:
Then, based on invisible
property, I thought the page would hide/show as expected, but the variable isSAOnly
is always false
as the service did not get injected properly I assume.
So my question is: Is it possible to inject a service to route.provider.ts
(as I haven't done it before)? If so, what is the correct way to implement it?
There's a similar thread , but what I want is to combine both user's permission & role, since the those 2 could be very much overlapped.
Hope to hear from you guys soon.
Thanks.
I will check it again. Thank you so much.
Hi Support Team,
I've encountered this bug:
Since I can not access the the API (/identity/organization-units) as it belongs to the framework core. I hope support team can help me solve this bug Hope to hearing from you guys soon.
Thanks.
Thank you. So how does the security of .NET 6 compare to .NET 7?
Because I've just done some research, .NET 7 has faster performance indeed, but nowhere mentions the improvement of security between 2 versions, so I assume it's pretty much the same, doesn't it?
Hi Supporting Team,
I'm planning for a major version upgrade in expecting for security enhancement. I've read through the changed logs but seemed not to catch as many related information about it. So I have a few things to consider:
Identity Server
with OpenIddict
? Does it have anything to do with security enhancement?Could you guys share your thoughts about it?
Hi, is there any update?
I tried to put modelBuilder.UseGuidCollation(string.Empty);
in DbContextModelCreatingExtensions
instead of DbContext
and run migration, the parameter collations for newly created column are all disappeared, which is good, but it also alters current columns collation:
Because current columns use default collation, their collation parameter shouldn't be added, and surely not ascii_general_ci
.
Could you guy take a look at this?