11.07.2015 Views

Borland VisiBroker® 7.0 - Borland Technical Publications

Borland VisiBroker® 7.0 - Borland Technical Publications

Borland VisiBroker® 7.0 - Borland Technical Publications

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Associating a LoginModule with a realmSyntax of a realm entryNoteEach realm entry has a particular syntax that must be followed. The following codesample shows the generic syntax for a realm entry://server-side realms for clients to authenticate againstrealm-name {loginModule-class-name required|sufficient|requisite|optional[loginModule-properties];...};The semicolon (“;”) character serves as the end-of-line for each LoginModule entry.The following four elements are found in the realm entry:■Realm Name—;the logical name of the authentication realm represented by thecorresponding LoginModule configuration■■■LoginModule Name—;the fully-qualified class name of the LoginModule to be usedAuthentication Requirements Flag—;there are four values for this flag—required,requisite, sufficient, and optional. You must provide a flag value for eachLoginModule in the realm entry. Overall authentication succeeds only if all requiredand requisite LoginModules succeed. If a sufficient LoginModule is configuredand succeeds, then only the required and requisite LoginModules listed prior to thatsufficient LoginModule need to have succeeded for the overall authentication tosucceed. If no required or requisite LoginModules are configured for an application,then at least one sufficient or optional LoginModule must succeed. The four flagvalues are defined as follows:■■■■required—;the LoginModule is required to succeed. If it succeeds or fails,authentication still continues to proceed down the LoginModule list for eachrealm.requisite—;the LoginModule is required to succeed. If it succeeds,authentication continues down the LoginModule list in the realm entry. If it fails,control immediately returns to the application—that is, authentication does notproceed down the LoginModule list.sufficient—;the LoginModule is not required to succeed. If it does succeed,control immediately returns to the application—again, authentication does notproceed down the LoginModule list. If it fails, authentication continues down thelist.optional—;the LoginModule is not required to succeed. If it succeeds or fails,authentication still continues to proceed down the LoginModule list.LoginModule-specific properties—;each LoginModule may have properties thatneed to be provided by the server administrator. The necessary properties for eachLoginModule provided by <strong>Borland</strong> are described below.Chapter 3: Authentication 31

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!