JWT Authenticator for Jenkins

Hi All,

I have integrated our Jenkins instance with Conjur enterprise successfully leveraging JWT authenticator. Authentication is also successful and Jenkins pipeline credentials store gets populated with secrets. The question I am having is, why JWT always uses a particular pattern for its host ID to authenticate with Conjur? It always uses “audience/jenkins_full_name” from JWT claim to build a logical host ID and tries to authenticate, if a host ID with same format exists in Conjur, authentication works otherwise it fails with error “… failed to authenticate with authenticator authn-jwt service prod:webservice:conjur/authn-jwt/xxxx: CONJ00007E ‘host/xxxxxx’ not found”.

Seems we are bound to create host ID with above format always during Host ID policy creation. Can’t we control this behaviour of authenticating with one particular pattern?