Borland VisiBroker® 7.0 - Borland Technical Publications

ChapterChapter12Security SPIfor C++Plugin Mechanism and SPIsThis section describes the Service Provider Interface (SPI) classes as defined forVisiSecure for C++. These SPI classes provide advanced security functionality andallow other security providers to plug their own implementation of security services intoVisiSecure for use within the Borland Deployment Platform.VisiSecure for C++ provides interfaces for you to plug in your own securityimplementations. In order for the ORB to find your implementation, all plugins must usethe REGISTER_CLASS macro provided by VisiSecure to register your classes. The name ofthe class must be specified in full together with its namespace upon registration.Namespace must be specified in a normalized form supported by VisiSecure, usingeither a '.' or '::' separated-string starting from the outer namespace. For example:MyNameSpace {class MyLoginModule {......}}Thus MyLoginModule shall be specified as either MyNameSpace.MyLoginModule orMyNameSpace::MyLoginModule.There are six pluggable components:■LoginModules: You can implement their own login models by extendingvbsec::LoginModule. To use the login module, you need to set it in the authenticationconfiguration file, just like any other login module.■■Callback handlers: You can implement their own callback by extendingvbsec::CallbackHandler. To use the callback, you need to set it in the authenticationconfiguration file, just like any other callback handler.Identity adapters, Mechanism adapters, and Authentication Mechanisms:these interfaces are provided for users to implement their own authenticationmechanisms and identity interpretations. IdentityAdaptor is to interpret identities,MechanismAdaptor is a specialized identity adaptor which also changes targetinformation. AuthenticationMechanism is a pluggable service to authenticate users.Chapter 12: Security SPI for C++ 117