XrdHttp does not populate the XrdSecEntity.prot field

[esindril]

Some OFS plugin implementations i.e. EOS rely on the type of protocol the access is being done to properly redirect the clients to different storage nodes and ports. When a requests comes from XrdHttp the protocol information is missing from the XrdSecEntity.prot filed. This is present however in the tident fields but this looks like a hack and misleading since the tident info is totally different when access is done through the XRootD protocol.

Could this info be added to the XrdSecEntity object?

Thanks,
Elvin

[abh3]

Hi Elvin, Indeed, this has been done for R5. Adding in a proper way breaks ABI. That's why we waited until R5 to do so. Look at XrdSecEntity::pros. Andy

…

On Wed, 22 Jan 2020, Elvin Sindrilaru wrote: Some OFS plugin implementations i.e. EOS rely on the type of protocol the access is being done to properly redirect the clients to different storage nodes and ports. When a requests comes from XrdHttp the protocol information is missing from the XrdSecEntity.prot filed. This is present however in the tident fields but this looks like a hack and misleading since the tident info is totally different when access is done through the XRootD protocol. Could this info be added to the XrdSecEntity object? Thanks, Elvin -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #1122

[ffurano]

Ah, I was remembering that there was something behind, because it used to be populated in previous versions.
What shall we do with this ticket then?

[abh3]

Let me see how to fix this. You are correct.

[abh3]

This has been fixed in R5.