Authentication
From Visual WebGui Wiki
| This article missing it's contents and needs writing. Please help contributing to this wiki and add contents. |
Contents |
Authentication in Visual WebGui and ASP.NET
Future contents
This article should discuss all the aspects of Authentication in Visual WebGui including discussion of that Visual WebGui and ASP.NET currently use seperate authentication methods. Samples of authentication in Visual WebGui, ASP.NET and combined Visual WebGui+ASP.NET sites should be supplied.
Tips and Tricks
Using authenticated ASP.NET and no authentication for WebGui
Visual WebGui uses a seperate mechanism for authentication than the one ASP.NET uses. We have an open task to allow some overlapping of authentication between the two. When it is done, it should should allow you to use ASP.NET authentication in a virtual directory that hosts both pure ASP.NET and a Visual WebGui application, at least partially.
Currently you can use ASP.NET authentication for the ASP.NET pages and no authentication on the Visual WebGui application. To accomplish this, you need to open an ASP.NET application, set the Web.config to have authentication of the pages. Create a Visual WebGui application and copy the WebGui section and all the other Visual WebGui relevant section in the Web.config file to the Web.config file of the ASP.NET application.
See also
Samples of use
- Find what is the target form - with authentication and within Logon form
- Demo for the new 6.4 per form authentication
SDK Version highlights
References
Forum threads
- Authentication for both Visual WebGui and ASP.NET
- Forms Authentication in Visual WebGui
- Logging in with single-sign-on part 1 and part 2
- Windows Identity Impersonation
- Getting the logged in user and domain
- Logon/Register form with email activation
- Automatic Logout
- Automatic Logout when user Idle (and here)
- Intercepting the Idle event and (possibly) handle KeepConnected requests differently amongst users
- Redirecting to login page when session expires
- Redirecting to login page when session expires
- Overriding Timeout.HTM via a Theme (see also Themes)
- Setting IsLoggedOn = False does not destroy ASP.NET session and Form.Load might not fire on next login (+ some ideas for different implementations of authentication)
- ASP.NET will by default authenticate to SQL with credentials running the application pool
- Integrated authentication creates excessive logon boxes - solved by static resources = On, and allow write to Route folder
- Passing Forms Authentication Cookie to HttpContext.User
Code samples
- ASP.NET Forms Authentication Sample
- Captcha sample (converting the sampe to more recent Visual WebGui version)
Other references
- MSDN: How to use Windows Authentication in ASP.NET 2.0
- Recipe: Enabling Windows Authentication within an Intranet ASP.NET Web application
- MSDN: Hot to use Windows Impersonation and Delegation in ASP.NET 2.0
- Ajax and timeouts
- Just Geeks: ASP.NET Session timeouts
