Direct links to fixes
Closed as program error.
Env: Linux Product: Secure Proxy v.3.2.00, Patch 4, Build 106 We have identified a problem where we ended up with two node entries in the same netmap where the nodes are the same except for case, ie.ppx008/PPX008. What we found was that this second entry was created because the remote was a windows node and it was entered to match the server node name case. The connections were using the security settings on the lower case entry for all connections. We would like to determine if the C:D and SSP systems truely normalizes all node names so that case doesn't matter when making connections and checking netmap entries. Based on the results of that answer, we would then expect that a bug/enhancement be entered to prohibit duplicate entries from being allowed in SSP. On the same note, the search function would need to be updated to return any case that matches the letters of a search, today it is case sensitive as well.
STRRTC - 347314 RJ/RJ Circumvention: None
Using the SSP configuration GUI for the CD netmap, the administrator is able to add a duplicate node using the same name if they use mixed case.
Now use a case-insensitive search for duplicate node names within the CD netmap before saving a new nodename.
Reported component name
STR SECURE PROX
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
STR SECURE PROX
Fixed component ID
Applicable component levels