the current reverse proxy federation role assumes that federation module is available on the reverse proxy server and searches for the federation ID on the reverse proxy instance and fails as there is no reverse proxy instance.
I have changed the appliance host variable in the task to get the role working but thats may not be a good idea. I guess we can define a new variable or do something similar to search mapping rule.
name: Lookup a Federation ID - {{config_reverseproxy_federation_name}}
isam:
appliance: "{{ Policy_Server_inventory_hostname }}"
username: "{{ username }}"
password: "{{ password }}"
lmi_port: "{{ lmi_port }}"
log: "{{ log_level }}"
force: "{{ force }}"
action: ibmsecurity.isam.fed.federations.search
isamapi:
name: "{{ config_reverseproxy_federation_name }}"
register: ret_obj
when: config_reverseproxy_federation_name is defined
the current reverse proxy federation role assumes that federation module is available on the reverse proxy server and searches for the federation ID on the reverse proxy instance and fails as there is no reverse proxy instance.
I have changed the appliance host variable in the task to get the role working but thats may not be a good idea. I guess we can define a new variable or do something similar to search mapping rule.