This section contains the following topics:
Patch Required for Custom Agents Running on HP-UX
Running C Sample Program with a 4.x Agent Requires Setting an Environment Variable [156186]
Configuration Issue with the smpolicyapi Samplr on UNIX platforms
Hierarchical Realms Not Supported in the Java PM API
Constants Missing from Java Policy Management API (13348)
Attributes Terminated with a Space in Java (13712)
Extra ServerDef Object Created with Java AgentAPI.getConfig() (14841)
Java SmPolicyApiImpl.search() cannot search for a Domain Object (15133)
Sort Order in a Java SmDMSCurson Object Cannot Be Empty (15317)
General Password Validation Errors in C (16787)
Java Method getConfig() Fails on Windows (39780)
Before you install a custom agent created with the Agent API on an HP-UX machine, install the following HP patch on the agent machine:
PHSS_24303 Id & linker tools cumulative patch
This patch is available at the HP web site.
Setting the environment variable for FIPs only is required for running the SmAgentAPI 'C' Samples for the 4x Agent connection to work. Make sure that this environment variable is set as follows:
export CA_SM_PS_FIPS140=ONLY.
After setting this environmental variable the SmAgentAPI 'C' Samples started working.
This setting is not required for 5.x agents.
Building the smpolicyapi sample program on Unix/Linux systems requires access to several Policy Server shared libraries and the NETE_PS_ROOT environment variable set to point to them. This may be accomplished by installing the Policy Server on the system with the SDK and using ca_ps_env.ksh to set the environment.
Hierarchical realms are not supported in the Java Policy Management API.
The Java class com.netegrity.sdk.policyapi.SmPasswordPolicy is missing the following constants:
|
Constant Name |
Constant Value |
|
Sm_PasswordPolicy_StopPriorityChaining |
0x00000080 |
|
Sm_PasswordPolicy_ExpireDisablePassword |
0x00000100 |
|
Sm_PasswordPolicy_FailuresDisablePassword |
0x00000200 |
|
Sm_PasswordPolicy_ForceCase |
0x00000400 |
|
Sm_PasswordPolicy_CaseSelect |
0x00000800 |
|
Sm_PasswordPolicy_CaseBits |
0x00000c00 |
|
Sm_PasswordPolicy_StripLeadingWhiteSpace |
0x00001000 |
|
Sm_PasswordPolicy_StripTrailingWhiteSpace |
0x00002000 |
|
Sm_PasswordPolicy_StripFlankingWhiteSpace |
0x00003000 |
|
Sm_PasswordPolicy_StripEmbeddedWhiteSpace |
0x00004000 |
|
Sm_PasswordPolicy_WhiteSpaceBits |
0x00007000 |
|
Sm_PasswordPolicy_PreProcessBits |
0x00007c00 |
Workaround: If you need to set these values, use the literal values directly instead of referencing the constant name.
When decodeSSOToken() returns, each attribute (byte array) returned in the AttributeList parameter is terminated with a space character.
Workaround: Before you use the session specification and session id attributes in a login() call to validate the session, trim the terminating space from each byte array.
If the Java AgentAPI.getConfig() method is used to read the configuration file, it creates an InitDef object having one more ServerDef object than is actually present. The extra object does not point to any Policy Server and is just an empty object.
In package com.netegrity.sdk.policyapi, the method PolicyApiImpl.search() returns an empty list when the object type to search for is type Domain, even if valid search parameters are given.
In the Java DMS API, any call (such as search(), getGroups(), and getMembers() ) that uses an SmDmsCursor object with an empty sort order will fail.
Password validation error IDs are reported in the nMsgId parameter of Sm_PolicyApi_GetPasswordMsg(). Specific error IDs are enumerated in Sm_PolicyApi_PasswordMsgId_t. Any error ID that is not enumerated in Sm_PolicyApi_PasswordMsgId_t should be considered a general password validation error. General password validation error IDs are reported in nMsgId when Sm_PolicyApi_GetPasswordMsg() returns -38.
In the Java class AgentAPI, the method getConfig() fails because it cannot locate the specified agent. This error only occurs on Windows platforms.
|
Copyright © 2012 CA.
All rights reserved.
|
|