Borland VisiBroker® 7.0 - Borland Technical Publications

More documents

Recommendations

Info

Enabling certificate passthrough to the Borland web containerConfiguring the mod_iiop IIOP connector of the httpd.conf file toforward SSL authenticationAs part of the certificate passthrough feature, a new IIOP configuration directive hasbeen added. The IIopEnableSSLExport directive instructs the IIOP connector to forwardSSL requests.If the IIopEnableSSLExport directive is enabled and a client request is set as secure (hasa type of https), then the IIOP connector will attempt to locate a set of environmentvariables. If a set of environment variables are found, then the IIOP connector forwardsthe data on to the Borland web container as part of the request.Modify the httpd.conf file located in: /var/domains//configurations//mos//conf byun-commenting the appropriate directives, shown here:LoadModule iiop2_module C:/BDP(b414)/lib//mod_iiop2.dllIIopLogFile C:\BDP(b414)\var\domains\base\configurations\j2eeSample/mos/ApacheWebServer/logs/mod_iiop.logIIopLogLevel errorIIopClusterConfig C:\BDP(b414)\var\domains\base\configurations\j2eeSample/mos/ApacheWebServer/conf/WebClusters.propertiesIIopMapFile C:\BDP(b414)\var\domains\base\configurations\j2eeSample/mos/ApacheWebServer/conf/UriMapFile.properties# Directive: IIopLookupLocalRefs true | false# Purpose: Allows apache to override the UriMapFile mapping if the reference isfound in the local doc tree.# Default: false - by default mod_iiop2 will not look for local referencesprior to dispatching a matching reference to# tomcat.##IIopLookupLocalRefs true### Directive: IIopChunkedUploading true | false# Purpose: Determines whether mod_iiop2 will attempt to chunk POSTed data(uploads). Corresponds to the enabledChunking attribute of the BorlandWebContainer's IIOP connector.# Default: false - Mod_iiop2 will not attempt to chunk uploaded data.##IIopChunkedUploading true## Directive: IIopUploadBufferSize n# Purpose: Allows mod_iiop to control the size of the 'chunk; of data POSTed tothe Borland WebContainer as part of a chunked upload. This directive isignored if IIopNoChunkedUploading is set to true.# Default: 4096##IIopUploadBufferSize 4096## Directive: IIopReapIdleConnections n# Purpose: Directs the VisiBroker orb to attempt to reap 'n' idle connectionsfrom the orb connection pool after every HTTP request. This can improveperformance on systems that have limited network resources.82 VisiBroker Security Guide
Security for the Borland web container# Default: none - by default mod_iiop2 does not request the orb to reap idleconnections.##IIopReapIdleConnections 50# uncomment the following to enable the "certificate passthrough" feature ofthe IIOP connector# Note: you must have already un-commented the SSLOptions directive of themod_ssl module earlier#IIopEnableSSLExport trueSecurity for the Borland web containerIn order to protect access to your web resources, you must secure those resources.The following steps are required for securing web resources using VisiBroker:1 Set up security for your Borland web container2 Set up security for each web applicationSecuring your Borland web containerBy default, the Borland web container is set up to use the Borland Security ServiceRealm (BSSRealm). To secure your Borland web container, you need to complete thefollowing:1 Enable security2 Configure Security authentication3 Configure Security authorizationSecuring your web applicationThe VisiBroker Server allows you to set security for each of your web applications byprotecting the URLs with which the application's resources are associated. To secure aweb application, you must first decide which URLs you want to protect. Once youprotect a URL, a user is not able to access it without entering a valid user name andpassword.Once you identify a web resource collection (servlets, JSPs, HTMLs, Gifs, and such)and the associated URLs your want to protect, the steps to securing the webapplication are:1 Define new security roles: Assign users to a security role which is used to determinewho accesses the web resources and what actions are allowed when using the webresources by way of a web browser.2 Define the security constraints for the specific web resource files: Protect the URLPatterns that map to certain servlets and JSPs.3 Set up a login: Set the login option which controls the access to the servlets andJSPs through their URL patterns.For example, you may set up a “Developer” security role that can access the webresources of the example.war file which contains the URL Pattern, jsp/security/servlet/*.jsp.Chapter 8: Security for the Web components 83
Page 1 and 2:
Security GuideBorlandVisiBroker ®
Page 3 and 4:
ContentsChapter 1Introduction to Bo
Page 5 and 6:
Security for the Borland web contai
Page 7 and 8:
Chapter1Introduction to Borland Vis
Page 9 and 10:
VisiBroker DocumentationImportant
Page 11 and 12:
Contacting Borland support■■■
Page 13 and 14:
Chapter2Getting Started with Securi
Page 15 and 16:
Basic security model■■■■Web
Page 17 and 18:
Distributed environments and VisiSe
Page 19 and 20:
Authentication and IdentificationAu
Page 21 and 22:
Authentication and IdentificationDi
Page 23 and 24:
Secure TransportationSecure Transpo
Page 25 and 26:
Context PropagationContext Propagat
Page 27 and 28:
Context PropagationTrusting Asserti
Page 29 and 30:
Using IIOP/HTTPSHere are several ex
Page 31 and 32:
ChapterChapter 3AuthenticationJAAS
Page 33 and 34:
Authentication mechanisms and Login
Page 35 and 36:
LoginContext class and LoginModule
Page 37 and 38: Associating a LoginModule with a re
Page 39 and 40: Borland LoginModulesThe elements in
Page 41 and 42: Borland LoginModulesLDAP LoginModul
Page 43 and 44: Server and Client IdentificationIn
Page 45 and 46: Server and Client IdentificationCre
Page 47 and 48: Server and Client IdentificationCli
Page 49 and 50: ChapterChapter4AuthorizationAuthori
Page 51 and 52: Defining access control with Role D
Page 53 and 54: Authorization domainsTo accomplish
Page 55 and 56: CORBA authorizationwhere is a taut
Page 57 and 58: Chapter5Configuring Security Profil
Page 59 and 60: Security ProfilesEnabling SecurityF
Page 61 and 62: Security ProfilesConfiguring Authen
Page 63 and 64: Security ProfilesTo access the Auth
Page 65 and 66: Security ProfilesWorking with Autho
Page 67 and 68: Security ProfilesAdding and Removin
Page 69 and 70: Associating a Profile with a Domain
Page 71 and 72: Chapter6Making Secure Connections (
Page 73 and 74: Steps to secure clients and servers
Page 75 and 76: Examining SSL related informationEx
Page 77 and 78: Chapter7Making Secure Connections (
Page 79 and 80: Steps to secure clients and servers
Page 81 and 82: Creating Custom PluginsLoginModules
Page 83 and 84: ChapterChapter8Security for the Web
Page 85 and 86: Security for the Apache web serverC
Page 87: Enabling certificate passthrough to
Page 91 and 92: Three-tier authorization schemeNote
Page 93 and 94: Chapter9Security Properties for Jav
Page 95 and 96: Security Properties for JavaPropert
Page 97 and 98: Chapter10Security Properties for C+
Page 99 and 100: Security Properties for C++Property
Page 101 and 102: Chapter11VisiSecure for C++ APIsCha
Page 103 and 104: General APIUse this to login to the
Page 105 and 106: General APISets the cipher suites t
Page 107 and 108: General APIReturnsA set of the publ
Page 109 and 110: SSL APISSL APIThis section explains
Page 111 and 112: SSL APIclass CipherSuiteNameThis cl
Page 113 and 114: SSL APIExceptionsCORBA::BAD_OPERATI
Page 115 and 116: Certificate APICertificate APIThis
Page 117 and 118: Certificate APIclass CORBAsec::X509
Page 119 and 120: QoP APIQoP APIThe following section
Page 121 and 122: Authorization APIAuthorization APIT
Page 123 and 124: ChapterChapter12Security SPIfor C++
Page 125 and 126: ProvidersProvidersTable 12.1Each pr
Page 127 and 128: vbsec::CallbackHandlervbsec::Callba
Page 129 and 130: vbsec::AuthenticationMechanismsMeth
Page 131 and 132: vbsec::TargetReturnsExceptionsArgum
Page 133 and 134: vbsec::Resourcevbsec::ResourceThe R
Page 135 and 136: vbsec::AttributeCodecFor the provid
Page 137 and 138: vbsec::PermissionCollectionvbsec::P
Page 139 and 140:
vbsec::InitOptionsvbsec::InitOption
Page 141 and 142:
IndexSymbols... ellipsis 4.defaultA
Page 143 and 144:
Iidentitiessetting up 36setting up
Page 145 and 146:
security (C++)AttributeCodec 119, 1
Page 147 and 148:
VisiSecure APIs (C++) 95VisiSecure
show all

Borland VisiBroker® 7.0 - Borland Technical Publications

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

Delete template?

Save as template?