Use Case - Application Security
Security administrators of large application systems, based on Java, CORBA, .NET, IMS, CICS or
other architectures, know how tedious it is to manage users and access rights. Authorizations for
the many services and transactions which people can use, and the access control for data like
contracts, documents or bank accounts often make administration a nightmare.
On the other hand, tight development budgets only allow to include the most essential
functions in the administration interfaces, transparency is low and administrative effort is high.
An integration of application security and its fine-grained authorizations in cross-platform
identity management systems could bring substantial relief – but most identity management systems
do not offer proper support for this task.
The SAM aConnect component of SAM Jupiter improves this situation without having to modify
the existing applications.
SAM aConnect
- Reduces complexity of administering services, transactions and data by using a business language oriented, rule-based approach
- Offers a convenient administration GUI for application security
- Integrates application security seamlessly within the enterprise provisioning solution.
For example, there's Mr Jones. He works in the Plymouth branch office of a large banking
institution.
Mr. Jones has been assigned to substitute Mrs Trethowan for some months as a teller in the
Saltash branch while Mrs Trethowan is on maternity leave.
The temporary revoking of access rights for Mrs. Trethowan is also a very simple task in SAM
aConnect: The teller role just has to be deactivated for the time of the absence.
Comparing Classical administration with SAM aConnect, the advantages of SAM aConnect become
obvious:










