Is it possible to have the Authorization header supported by context registration forwarding?

[sekiguchi-yohei]

Hi.

We are currently examining the possibility of using Orion-LD context registration in our project. In our project, when transferring access in context registration, we want to transfer the Authorization header from the context broker to the context provider as well. I don't think Authorization header forwarding is currently supported, is it possible to have Orion-LD support it in the future?

[kzangeli]

I believe the X-Auth-Token HTTP header is already included in forwarded requests. Not 100% sure, might be I implemented that for notifications but not for forwarded requests ...

That said, forwarding is still very much a work in progress. The NGSI-LD API doesn't support it yet (we're working on it, but it's quite complex) and what is to be found in Orion-LD about forwarding is just a proof of concept, implemented only in the following two requests:

• GET /ngsi-ld/v1/entities/{entityId}
• PATCH /ngsi-ld/v1/entities/{entityId}/attrs/{attrName}

So, it might be a little premature to play around with forwarding still, using Orion-LD. Or any other NGSI-LD broker for that matter.

I know Scorpio has implemented a "NEC-style" forwarding (only supporting query on entities), but, that's of course also not NGSI-LD standard, as the NGSi-LD API still doesn't define how forwarding is supposed to work.

Now, if you're happy with testing our PoC, with the two requests that support forwarding, I'm happy to assist. Which exact HTTP header do you need to be included in the forwarded request?

[sekiguchi-yohei]

Thanks for the reply, Ken!

The X-Auth-Token was indeed forwarded. However, Authorization cannot be forwarded as an HTTP header ... I am assuming that Authorization is the HTTP header to be included in the forwarded request, but is it difficult to forward the Authorization header?

[kzangeli]

Authorization is just another HTTP header. No problem at all. Only, forwarding is not really implemented yet, so, not sure how interesting this is right now. Are you OK with only using the following two requests for forwarding?:

• GET /ngsi-ld/v1/entities/{entityId}
• PATCH /ngsi-ld/v1/entities/{entityId}/attrs/{attrName} ?

More will come, but I can't really say when ...

[kzangeli]

Fixed it in PR #913