Mathia Pagani

yes both fits and irods_http_api clients are configured in Indigo IAM instance with the scope `profile` checked. > if it is only requested during token request, it does not appear...

I think the issue lies in the authorization grant that is issued by Indigo IAM following the GET request from the FITS client to the authentication endpoint of the iRODS...

> If I understand correctly, you use the `authorization code` grant type to obtain the access token, right? or `client_credentials` flow? yes that's correct. We use the authorization code grant...

I fixed it but have another problem. ## How I fixed it I checked the source code of the iRODS http api and found that the authenticate endpoint create an...

I just found out while checking checking the AT that it seems that the signature is not valid (testing with JWT). I paste the token here, since the client_id of...

Thanks for confirming that. I got this answer back from iRODS team: >This is because the iRODS HTTP API does not act as an OAuth protected resource at this moment....

> I'm not sure I understand the whole architecture of your application (FITS + iRODS), but one thing that you can try as a short-term workaround is to manage the...

> Hi, > > from our point of view the next implementation is the correct OAuth flow to be used > > * FITS interface to log-in with IAM and...

> The link quoted above points to this repository rather than the correct location... [irods/irods_client_http_api#155](https://github.com/irods/irods_client_http_api/issues/155) > > We welcome input and use cases as we continue to build out our...

Hi @rmiccoli, Thanks for your response. I'm a bit unsure where to add the .yml file exactly. I've realized my initial questions may not have been clear. I made a...