Borland VisiBroker® 7.0 - Borland Technical Publications

Security Properties for C++Property Description Defaultvbroker.security.login.realmsvbroker.security.vaultvbroker.security.identity.reactiveLoginvbroker.security.authDomainsvbroker.security.domain..rolemap_pathvbroker.security.domain..rolemap_enableRefreshvbroker.security.domain..rolemap_refreshTimeInSecondsvbroker.security.peerAuthenticationModeThis gives a list of comma-separated realms to login to. Thisis used when login takes place, either through propertyvbroker.security.login (set to true) or API login.This property is used to specify the path to the vault file. Thisproperty will take effect regardless of whethervbroker.security.login is set to true or false.When set to true, the security service behaves as follows. Ifthe security service cannot find an identity for any of thetargets supported by a server it is attempting to communicatewith, it then attempts to acquire credentials for one of thetargets in the target object's IOR. If a correspondingauthentication realm is available for this target (that the userchooses to provide credentials for), then authentication isalso attempted locally.Reactive login requires a callback handler to be set eitherusing the appropriate property or at runtime by calling theappropriate method. The default handler isHostCallbackHandler.Specifies a comma-separated list of available authorizationdomains. For example:vbroker.security.authDomains=domain1,domain2Specifies the location of the RoleDB file that describes theroles used for authorization. This is scoped within the domain specified in: vbroker.security.authDomains.When set to true, enables dynamic loading of the RoleDB filespecified invbroker.security.domain..rolemap_path property.The interval of dynamic loading is specified by propertyvbroker.security.domain..rolemap_refreshTimeInSeconds.n/an/atruen/an/afalseSpecifies the rolemap refresh time in seconds. 300Sets the peer authentication Mode. Possible values are:REQUIRE—Peer certificates are required to establish aconnection. If the peer does not present its certificates, theconnection will be refused. Peer certificates will also beauthenticated, if not valid, the connection will be refused. Ifrequired, transport identity can be established using thesecertificates. In this mode, peer certificates are not required tobe trusted.REQUIRE_AND_TRUST—Same as REQUIRE mode, except thatthe peer certificates need to be trusted, otherwise theconnection will be refused.REQUEST—Peer certificates will be requested. The peer is notrequired to have certificates; no transport identity will beestablished when peer does not have certificates. However,if a peer does present certificates, the certificates will beauthenticated; if not valid, the connection will be refused. Ifrequired, transport identity can be established using thesecertificates. In this mode, peer certificates are not required tobe trusted.REQUEST_AND_TRUST—Same as REQUEST mode except that thepeer certificates need to be trusted, otherwise the connectionwill be refused.NONE—Authentication is not required. During handshake, nocertificate request will be sent to the peer. Regardless ofwhether the peer has certificates, a connection will beaccepted. There will be no transport identity for the peer.REQUIRE_AND_TRUST92 VisiBroker Security Guide