 |
Authentication in RBAC consists of verifying
the identity of the user through a two step process:
• Identification:
Stating who you are;
• Authentication: Proving who
you are. |
Two types of needs:
• You may need to create a list of user accounts/passwords
from scratch.
• You may already have Windows accounts stored in Active Directory
and need to re-use it at application level.
The solution:
Visual Guard PowerBuilder supports login/passwords authentication.
A user account declared in Visual Guard is available for all your
PowerBuilder applications.
It supports the following authentication modes:
• Visual Guard Accounts (created and managed by Visual Guard)
• Windows Accounts (local account or Active Directory account)
(coming soon)
Windows accounts/Active Directory
If you use the Windows authentication mechanism, passwords are created,
stored and administered in Active Directory. You will be able to
re use Windows authentication mechanism to identify users of your
applications, and then assign Visual Guard profiles and permissions
to this user.
Single
sign-on
If you use Active Directory to manage user accounts you may want
to implement a single sign-on process: once a user is logged on
in a Windows session, any application opens without asking for further
credentials.
Visual Guard supports Single Sign-On configurations for Windows
accounts.
Visual
Guard PowerBuilder Accounts
Visual Guard PowerBuilder has its own membership provider to manage
user accounts and passwords.
Credentials are stored in the Visual Guard repository.
Resources:
 See
a demo for PowerBuilder
Getting
started
Visual Guard Architecture
How does it work?
Receive an evaluation version
Visual
Guard for .NET
|
