Dears,

I would like to extract a custom token that comes in the request headers of my client using as the identity extraction the Processing Metadata.

I define the object:

Metadata Category -> Custom Header

Metadata Item -> custom-token (due to the XML Info file - Custom Token)

Custom Data Source -> the desired header.

However the extraction is made but it doesn't satisfy the XML Info file, so every request is rejected by policy.

¿Any ideas?

Thank you!

Regards,

SebasQuiroga

Hi,

change Metadata Item -> custom-token to Metadata Item -> token

--HP

Thank you HPernaa!

Dear HP,

Is it possible to add the same custom token in Metadata Item (token) with different Custom Data Source?

I tried to duplicate the Metadata Item - token- and changing for the new Custom Data Source - an other custom header - but it gives error.

Can you please explain what are you trying to achieve? If you want the automatic extraction and authentication to work, a duplicate item will most likely break the logic.

--HP

Dear HP.

Thanks for your answer,

The scenario is the following: at the beginning, clients were using in the header fields a custom token named - let's say for example - tokenName1, then as time passed, new clients start using for the same purpose a new token named for instance tokenName2; the idea is to extract both identities (Both custom tokens that actually refer to the same)using Processing Metadata.

Regards,

I get the following error from WebGUI when I try to duplicate the item: "Error: Metadata Item Name must be unique within each Meta Category" . So this is pretty clear. If you want the automatic extraction to work, then you have to rewrite the headers yourself using some custom transformation and then gradually enforce the clients to start using one single header.

--HP

Dear HP,

Thanks for your answer.