Wildcard usage in AgentName ACO value in Web Agent
search cancel

Wildcard usage in AgentName ACO value in Web Agent

book

Article ID: 225385

calendar_today

Updated On:

Products

SITEMINDER CA Single Sign On Agents (SiteMinder)

Issue/Introduction

When running a Web Agent, can wildcard * in AgentName be used in order to map any host to the single configuration?

This is to achieve the business requirement to add "automatically" protection of new domains without having to add manually the new domain in the AgentName ACO.

Resolution

The AgentName ACO doesn't allow wildcards as * (1).

Reading the AgentName description further, the AgentName can be mapped to IP addresses like:

Example: <agent1>,192.168.1.0 (IPV4)
Example: <agent2>, 2001:DB8::/32 (IPV6)

As such, if the multiple domain names refer to the same IP address, all domains with the same given IP address will be protected.

Also, DefaultAgentName will be the default AgentName for any "not found mapping" in AgentName.

As such, the unique value from DefaultAgentName will be used.

So, maybe a combination of AgentName mapping with unique IP Address and a specific choice of the DefaultAgentName value might help to implement the requirement to add "automatically" protection of new domain.

Additional Information