Forum Discussion
So, I have this working, sort of.....
So utilizing iControl for .Net
I'm initializing and iControl Interface, but I'm getting some strange behavior I believe it's because I'm not properly tearing down the connection but I'm not sure.
So basically we're moving to RemoteRoles using RADIUS to ease administrative burdens, but we have an iControl app that we need to ensure works after the transition. So during testing of the iControl I'm switching the radius attributes returned for my login to simulate several user roles.
Setting a breakpoint at the User permissions I've noticed that once I connect and get a permission set, even if I close the application i keep getting the same permissions. If I chage the RADIUS attributed to get another role, when i re-launch the application and initialize the interface my User Permissions reflect the old role until some (unknown to me) timeout occurs, but the LTM GUI would reflect the new role immediately (ruling out and delay between RADIUS attribute changes vs. returned attributes). Once this timeout has elapsed (maybe 15 minutes?) and I re-initialize the iControl Interface the proper permissions are present.
How should I be tearing down / logging out of iControl when I'm finished with the interface? Currently I'm just setting it to null as I don't see a close / logout method.