RFC 1632:A Revised Catalog of Available X.500 Impl...
RFC-Ref

authentication


Click on the red underlined text to get to the source

... It supports the referral, chained and multi-casting modes of operation, access control lists, simple authentication, management of knowledge information (for distribution, shadows and ...
... Agreements Strong authentication in X.509 is not yet implemented. (Password ...
... Agreements [NIST-88]. OSI Access and Directory only supports simple authentication or no authentication. OSI Access and Directory ...
... NIST-88]. OSI Access and Directory only supports simple authentication or no authentication. OSI Access and Directory complies with all static and dynamic requirements ...
... RDN operation - Abandon operation - Strong Authentication - Schema checking ...
... Agreements). Strong authentication according to X.509 and an XDS/XOM convenience library will be included in the next version ...
... Protocol Specifications *x.509 describes simple and strong authentication. HP X.500 Distributed Directory supports simple authentication ...
... authentication. HP X.500 Distributed Directory supports simple authentication. Strong authentication is not supported in the current release due to ...
... Distributed Directory supports simple authentication. Strong authentication is not supported in the current release due to limited market demand. ...
... DSAs and DUAs) 88 Standard compliant: Strong authentication not yet implemented. No plans for support of the 1992 Standard. ...
... Services is a complete implementation of the 1988 X.500 Recommendations with the exception of strong authentication as outlined in X.509. It is conformant to NIST ...
... DSAs and DUAs) 88 Standard compliant: Strong authentication not yet implemented. No plans for support of the 1992 Standard. ...
... DSAs and DUAs) [Same as dish] -- does not support strong authentication. No support for 1992 extensions needed. ...
... Version 1, with the following exceptions: - Strong authentication is not implemented (but hooks are provided for use with two packages). - QUIPU does not enforce the bounds constraints ...
... DIB or subtree administrative manager supported. Supports simple authentication with encrypted password. ...
... Object class and attribute definitions are enforced. Users may define their own. - Simple authentication is provided; strong authentication and signed operations are being tested operationally through TS ...
... definitions are enforced. Users may define their own. - Simple authentication is provided; strong authentication and signed operations are being tested operationally through TS-E3X's ...
... API supports the Basic Directory Contents (BDCP), the MHS Directory User (MDUP) and the Strong Authentication (SAP) packages with minor limitations. A proprietary mechanism for defining new ...
... address mail. Authentication Services - Verifies the login name and password of ...
... service administration programs such as login authentication, the database management ...
... tree searches are not supported, nor does the product support chained adding, modifying, or deleting. Simple authentication is supported, but strong authentication is not. ...
... adding, modifying, or deleting. Simple authentication is supported, but strong authentication is not. In the future, the 1992 extensions to the X.500 ...
... 88 standard compliant: Delete and Add operations, and strong authentication not implemented. There are no facilities to modify the RDNs of entries. ...
... DSAs and DUAs) 88 Standard compliant: Strong authentication not yet implemented. No plans for support of the 1992 Standard. ...
... - Friendly editor of modifying Quipu ACLs. - Rebinding - authenticated and to named DSA. - Full configuration of DAP ...
... version 2 except X.509 strong authentication not implemented (under development). NEXOR is committed to migrate XT-DUA ...
... version 2 except X.509 strong authentication not implemented (under development). NEXOR is committed to migrate XT-QUIPU to the 1992 standards. ...



Google
Web
RFC-Ref