Does TIBCO API Exchange Gateway allow wildcards in Partner Data?
Article ID: KB0073705
Updated On:
| Products | Versions |
|---|---|
| TIBCO API Exchange | ALL |
Description
Here are sample entries from PartnerData.cfg:
partner_client01_cn_partner|client01_cn_partner|||||CN=client01.tibco.com,OU=Support,O=TIBCO,L=Arlington,ST=TX,C=US|CN=client01.tibco.com,OU=Support,O=TIBCO,L=Arlington,ST=TX,C=US||false||
partner_client02_cn_partner|client02_cn_partner|||||CN=client02.tibco.com,OU=Support,O=TIBCO,L=Arlington,ST=TX,C=US|CN=client02.tibco.com,OU=Support,O=TIBCO,L=Arlington,ST=TX,C=US||false||
partner_client_wildcardCN_partner|client_wildcardCN_partner|||||CN=*.tibco.com,OU=Support,O=TIBCO,L=Arlington,ST=TX,C=US|CN=*.tibco.com,OU=Support,O=TIBCO,L=Arlington,ST=TX,C=US||false||
Environment
All Supported Platforms
Resolution
APIX-G does an exact match on the SerialNumber and CAIssuer configured, for identifying a Partner.
So wildcards cannot be configured when creating Partner Data.
For the above examples, it won't be able to identify other SerialNumbers to 'partner_client_wildcardCN_partner'
So wildcards cannot be configured when creating Partner Data.
For the above examples, it won't be able to identify other SerialNumbers to 'partner_client_wildcardCN_partner'
Issue/Introduction
This articles provides inputs on using wildcards while creating Partner Data in APIX-G
Feedback
Yes
No
Powered by
