CA eTrust SiteMinder Developer's Guide for Java

More documents

Recommendations

Info

Server ClustersCluster failover occurs according to the following configuration settings:■Failover threshold. The minimum percentage of servers within a clusterthat must be available for Policy Server requests. If the number ofavailable servers falls below the threshold, failover to the next clusteroccurs.The failover threshold percentage applies to all clusters associated with theagent.To determine the number of servers that the percentage represents in anygiven cluster, multiply the threshold percentage by the number of serversin the cluster, rounding to the nearest integer. For example, with a 60-percent failover threshold for a cluster of five servers, failover to the nextcluster occurs when the number of available servers in the currently activecluster falls below 3.Set through: InitDef constructor that contains the failOverThresholdparameter.■Sequence of cluster failover. Each cluster is assigned a sequencenumber. When cluster failover occurs, SiteMinder sends subsequent PolicyServer requests to the next cluster in the cluster sequence.Set through: ServerDef.clusterSeq().Cluster FailoverIf your site uses clusters, you typically will have a primary cluster and one ormore backup clusters.The primary cluster is the cluster to which SiteMinder sends requests as longas the number of available servers in the cluster does not fall below thefailover threshold. If there are not enough available servers in the primarycluster, failover to the next cluster in the cluster sequence occurs. If thatcluster also fails, failover to the third cluster occurs, and so on.When All Clusters FailIf the number of available servers falls below the failover threshold in allclusters associated with the agent, policy operations do not stop. Requests aresent to the first cluster in the cluster sequence that has at least one availableserver.For example, suppose an agent is associated with two clusters—C1 containingthree servers, and C2 containing five servers.The failover threshold for anycluster associated with the agent is set at 60 percent.50 Developer's Guide for Java
TimeoutsThe following table shows the minimum number of servers that must beavailable within each cluster:ClusterServers inClusterPercentageFailoverThresholdNumericFailoverThreshold(MinimumAvailable Servers)C1 3 60 1C2 5 60 3Version Compatibility and Failover BehaviorIf the number of available servers falls below the threshold in each cluster, sothat C1 has no available servers and C2 has just two, the next incomingrequest will be dispatched to a C2 server with the best response time. After atleast two of the three C1 servers are repaired, subsequent requests are loadbalancedamong the available C1 servers.Agent API v6 is backwards-compatible with Agent API v5, allowing completeinteroperability between v5/v6 agents and the v5/v6 Agent APIs.TimeoutsAgents can enforce session timeouts or rely on the Policy Server to validateeach request. Typically, caching of user sessions or privileges by the agentrequires some form of timeout enforcement on the agent side. In this case,the agent is responsible for keeping track of last access time and knowingwhen the session is going to expire.Agents that do not cache can leverage the Policy Server’s enforcement oftimeouts. The following Java Agent API methods return the updated timeoutinformation after every call:■■■login()authorize()audit()Chapter 3: Agent API 51
Page 2 and 3: This documentation and any related
Page 5 and 6: ContentsChapter 1: Java API Overvie
Page 7 and 8: Make Policy Management API Requests
Page 9: Set Search Parameters When You Crea
Page 12 and 13: Code SamplesCode SamplesThe SiteMin
Page 14 and 15: Policy Management APIThe SiteMinder
Page 16 and 17: How Java Components Fit TogetherHow
Page 18 and 19: Java API FlowThere are two types of
Page 20 and 21: Java API FlowIf you do not already
Page 22 and 23: Java API FlowYou might already have
Page 24 and 25: Javadoc ReferenceJavadoc ReferenceT
Page 26 and 27: Connection ClassConnection ClassYou
Page 28 and 29: Result ClassInterpret a Result Obje
Page 30 and 31: Property ClassThe core methods of t
Page 32 and 33: Agent API Class HierarchyThe Agent
Page 34 and 35: Implement the Pure Java Agent API5.
Page 36 and 37: Connection to a Policy Server■■
Page 38 and 39: User Access to Resources5. Audit ca
Page 40 and 41: Java Agent API ServicesJava Agent A
Page 42 and 43: Authorization ServicesSession Termi
Page 44 and 45: Tunnel ServicesTunnel ServicesTunne
Page 46 and 47: Single Sign-on4. Custom agent creat
Page 48 and 49: Server ClustersAdvantages of Sessio
Page 52 and 53: Agent TypeAgent TypeThe Agent Type
Page 54 and 55: About Policy ManagementAbout Policy
Page 56 and 57: Policy Store Objects■■■■■
Page 58 and 59: Write a Policy Management Applicati
Page 60 and 61: Agent Configuration Object MethodsA
Page 62 and 63: General Object MethodsMethoddeleteD
Page 64 and 65: ODBC Query Scheme MethodsODBC Query
Page 66 and 67: Realm MethodsMethoddoImport()Descri
Page 68 and 69: Self-Registration MethodsSelf-Regis
Page 70 and 71: Utility MethodsMethodgetUserPolicie
Page 72 and 73: Retrieve Objects from the Policy St
Page 74 and 75: Authentication Scheme Configuration
Page 81: individuals might increase their in
Page 100 and 101:
Authentication Scheme Configuration
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 113 and 114:
Chapter 5: Authentication andAuthor
Page 115 and 116:
Shared InformationShared Informatio
Page 117 and 118:
Create a Custom Authentication Sche
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Use the Authorization API8. After t
Page 129 and 130:
Use the Authorization APIInterpret
Page 131 and 132:
Use the Authorization APIOther Clas
Page 133 and 134:
Use the Authorization APIActive Rul
Page 135 and 136:
Use the Authorization APITo modify
Page 137:
Use the Authorization API■■To e
Page 140 and 141:
The Required JAR File■■Adding a
Page 142 and 143:
Attribute-based DelegationAttribute
Page 144 and 145:
Implementation Class■SiteMinder a
Page 146 and 147:
Search ClassThe objects correspondi
Page 148 and 149:
Write a Directory Management Applic
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
SearchesSet Search Parameters When
Page 160 and 161:
SearchesSet the Search FilterThe se
Page 162 and 163:
SearchesSearch an OrganizationIn th
Page 164 and 165:
User Password StateThe following co
Page 166 and 167:
Restricted Methods■■SmDmsUser.a
Page 168 and 169:
Restricted MethodsMethodsearchForwa
Page 170 and 171:
Authentication Scheme Dialog • 11
Page 172 and 173:
getDmsContext() • 144, 166getDmsD
Page 174 and 175:
organizations in flat directories
Page 176 and 177:
SmApiResult class • 27SmApiSessio
show all

CA eTrust SiteMinder Developer's Guide for Java

Create successful ePaper yourself

Delete template?

Save as template?