c# - How to refresh AzMan access check cache? -
I have created a web application that uses Microsoft Host, and as long as you do not have multiple users works fine. I'm almost 100% sure that Ajman is caching the same thing for many users.
To make it a little easier, the problem I am seeing is that the user goes to A site and there is full access to the user, right access is provided and can work just fine. Then user b goes to the site, there is only access access, but because Azman has already seen full access to User A, it also fully accesses User B.
I'm creating the client reference when using the AddStringSids method because it is the only way that will work for every situation. Is there a problem in it? We did not keep this problem when we were making client references from a token.
I am using the exact code to create the following reference. The application has an IAzApplication2 variable, and ClientContext.SID is a securityIdentifier for the user in question
IAzClientContext2 cctx = app.InitializeClientContext2 ("AppNameHere", tap). Cctx.AddStringSids (new object [] {(object) as ClientContext.SID.ToString ()} object); Edit: I am not using the ASP.NET Roll Provider at all because the application should be aware of the roles. I'm only using COM API. Edit 2: Also, if User B is first logged in, User A does not enter, then no access. So it is only using the highest level.
I thought about removing this question, but I think it might be possible to leave here Better the stupid mistake is not caching any other help to AzMan check probes results for multiple users. The addStringSids method is not a problem The problem was in my code.
I had a stable variable that was holding the context of the client reference, and is created only once for the life of the application, not the life of the user requests. This is a stable variable due to which it has become the first person to reach access.
So this was a stupid programmer mistake, or SBCK (Small between the chair and keyboard) would call my boss, so if you are running a similar problem in ASP.NET, then check your variable and Make sure you do not have a fixed variable issue.
Comments
Post a Comment