Search results
From K5Wiki
Create the page "Kerberos library requirements" on this wiki! See also the search results found.
- The CCAPI is part of MIT Kerberos for Windows [KfW]. KfW runs on Windows XP, Windows Vista and Windows Termi ==Design Requirements ==22 KB (3,453 words) - 14:30, 3 April 2008
- ...ially do with file caches quite so safely. This will be important for the Kerberos Identity Manager project that Alexandra is working on (cf. http://web.mit.e =Functional Requirements=10 KB (1,610 words) - 19:46, 22 January 2008
- ...nt management tool. ~15 minutes to set up. Dangerous to attach ancillary requirements to a project. KK clarifies: you're talking about Steve's requirements? Yes. How to proceed?3 KB (407 words) - 23:50, 3 January 2011
- ...orm maintainers want to control the Kerberos UI on their platform. The [[Kerberos identity management API]] needs to interface with the platform specific UI ...very stable. Forward and backward compatibility between UI plugins and Kerberos will be required within a reasonably wide margin.2 KB (322 words) - 12:35, 22 January 2008
- ...er.ietf.org/drafts/draft-ietf-krb-wg-kerberos-referrals/ draft-ietf-krb-wg-kerberos-referrals]) support in the KDC and providing the mapping information to cli == Functional Requirements ==5 KB (811 words) - 00:13, 16 February 2010
- ...various communities and vendor products. Organizations that currently use Kerberos as a key element of their infrastructure wish to take advantage of its uniq ...rchitectural model for working towards a more cohesive and widely deployed Kerberos-based Web authentication infrastructure.99 KB (14,634 words) - 19:15, 29 October 2008
- ...on't supply them, are declared in k5-platform.h and defined in the support library (which practically everything in the tree links directly against). If you're writing new library code, pick a short prefix and stick with26 KB (4,074 words) - 18:11, 22 July 2023
- ...ies krb and builtin. The first of these folders will be designated for the Kerberos specific functionality, while the second directory will be a place-holder f == Functional Requirements ==4 KB (551 words) - 00:12, 16 February 2010
- ;S: one of the samba requirements as well. when kerberos is used in a complicated environment, want some consistent lockout. [across ...n Samba and active directory env, you want policy and state to not be like kerberos. Just want kdc. for novell, update lockout tracking state in kdb calls. d10 KB (1,781 words) - 23:56, 3 January 2011
- on kerberos, because Samba4, like Samba3, was built to use Samba4 and MIT's kerberos.51 KB (7,287 words) - 13:17, 2 September 2009
- ...anonymous pkinit from {{rfcref|6112}}. This project allows users to obtain Kerberos tickets even if they have no principal registered in a realm. Use cases in ==Functional Requirements==6 KB (878 words) - 16:43, 12 December 2012
- ...ce mandates the use of FAST; if a client supplies an armor ticket then the library requires the KDC to support FAST. == Functional Requirements ==7 KB (1,137 words) - 00:48, 16 February 2010
- ...environment (depending on the type of hardware, system,configuration) and requirements (optimization, FIPS certification etc). == Functional Requirements ==2 KB (337 words) - 13:58, 17 November 2010
- The following requirements are in scope for this project: The following requirements are out of scope:13 KB (2,135 words) - 14:25, 12 October 2011
- == Requirements == ...ages. This allows to link tickets to their initial TGT at any stage of the Kerberos exchange.14 KB (2,151 words) - 13:01, 29 October 2013
- ...pts of the default ccache, default keytab, and default client keytab for a library context. (The default client keytab is new in 1.11; see [[Projects/Keytab_ ...lt by setting KRB5CCNAME, tickets obtained using kinit on a system without Kerberos login integration will use the per-uid default in /tmp.6 KB (991 words) - 14:00, 29 November 2012
