What is "Principal", and what is meant by "Principal
authentication"?
- 1 Answers
- 2769 Views
- I also Faced
- E-Mail Answers
Answer Posted / rithi
Linda Gricius (March, 1998):
Principal authentication is the process of proving your
identity to the security enforcing components of the system
so that they can grant access to information and services
based on who you are. This applies to both human users of
the system as well as to applications.
A user or application that can authenticate itself is known
as a principal. A principal has a name that uniquely
identifies it.
For human users, the process of authenticating to the system
is informally known as "logging on". In a typical system, an
application is provided to collect information proving the
user's identity. This application is often referred to as
the "user sponsor". In order to successfully authenticate to
the system, it is important that a principal can provide
some proof that it is who it claims to be. Proof of
authentication is usually achieved by demonstrating
knowledge or possession of a "secret" known only to the
"real principal", such as a password or cryptographic key.
It is important that a successfully authenticated principal
can be given some unforgeable evidence that it has recently
authenticated, in order to prevent the principal from having
to continually re-authenticate itself to different parts of
the system. The unforgeable evidence that is returned to
authenticated principals is known as the principal's
credentials.
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
Explain do different corba implementations perform at significantly different levels?
How does corba support interoperability?
What would be the most suitable ORB products when buliding a small lab for evaluating, testing and implementing security functions in a CORBA system?
Can corba application be multi-threaded?
Can corba application have call back?
Give us high-level technical overview of corba?
Explain what is the reason to implement corba in client application application?
Explain are there important forms of asynchronous communication that are not supported directly by corba?
Does the existing Authorization Service of CORBASec scale in a "well" distributed-object environment?
Explain does corba define high level application architectures?
Explain can corba application be tuned for better performance?
What are the reason to avoid the development of multi-threaded corba application?
What are the shortcomings of CORBA Security service?
Is there a set of UML diagrams for the CORBASEC Specification?
Can corba allow servers to cause client side events or notifications?
