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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

ProvidersProvidersTable 12.1Each provider instance is created by the VisiSecure using a Java reflection API. Afterthe instance has been constructed, the initialize method, which must be provided bythe implementer, is called passing in a map of options specific for the implementation.The options entries are defined by the implementers of the particular provider. Usersspecify the options in a property file and the VisiSecure parses the property and passesthe options to the corresponding provider. The following table shows the properties forplugging in different provider implementations.Settings for Security Service Provider ImplementationsModule Name Property to set Interface to implement Options PrefixIdentityAdaptervbroker.security.identity. vbsec::IdentityAdapter vbroker.security.identity.adapter.adaptersAuthenticationMechanismAttributeCodecTrustProvidervbroker.security.identity.mechanismsvbroker.security.identity.attributeCodecsvbroker.security.trustProviderIn the preceding table:vbsec::AuthenticationMechanismsvbsec::AttributeCodecvbsec::TrustProvidervbroker.security.identity.mechanism.vbroker.security.identity.attributeCodec.vbroker.security.trust.trustProvider.■■■■The first column lists the provider module names.The second column lists the property you set to define each module. Use a commato separate multiple modules. For example, the following property has two additionalIdentityAdapter implementations installed for the ORB:vbroker.security.identity.adapters=ID_ADA1,ID_ADA2The third column gives the interface each implementation must implement. Theinterface defines a contract between the implementers and the core VisiSecure.The final column gives the options prefix for the specific module. The ORB parsesthe property file and passes the corresponding entries to each of the modules in theinitial method as the (Map options) parameter. For example, for the ID_ADA1IdentityAdapter defined in the previous example, all the entries with thevbroker.security.identity.adapters.ID_ADA1 prefix will be passed to the initialmethod of ID_ADA1 IdentityAdapter.Providers and exceptionsDuring the initialization, if anything goes wrong the initialize method should throw aninstance of InitializationException. For certain categories of providers, there can bemultiple instances with different implementations co-existing. Each of them is identifiedby the name within the VisiSecure system, which is passed as the first parameter in theinitialize method. While for some categories of providers there can be only oneinstance existing for the whole ORB (such as in the case of the TrustProvider, in thiscase, the initialize method has only one single parameter ?the options map.Chapter 12: Security SPI for C++ 119

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

Saved successfully!

Ooh no, something went wrong!