aalonsog's profile - activity

Here you will find the related documentation, with videos and tutorials https://catalogue.fiware.org/enablers...

Here you will find the related documentation, with videos and tutorials https://catalogue.fiware.org/enablers/identity-management-keyrock/documentation

It seems to be a problem with Cryptography lib. I see several forums in which developers propose solutions to it.

Hi! I recommend you to see FIWARE Academy videos to learn how to use Cloud Portal: https://edu.fiware.org/course/view.ph...

As OAuth2 and Keystone tokens are different, they should also have different expiration time parameters in the configuration. Please, could you implement it that way and contribute the code to the project?

Hi, Keystone tokens expiration time is configured in https://github.com/ging/keystone/blob...

Regarding OAuth2 tokens, right now the expiration time is not configurable. We have plans of adding this possibility soon.

Duplicated. Answer in http://stackoverflow.com/questions/39...

Hi, we have not performed tests yet. But if the token API has not changed, it should work.

I see in the GItHub issue you have finally solved the problem.

Thanks, it is fixed now. The right endpoint is http://cloud.lab.fiware.org:4730.

I don't understand what do you mean with "when logging out of our application, Horizon IDM redirects to its own login screen." IdM doesnt support single sign out. When you log out in Horizon you are of course redirected to its login page. When you log out on your app, it depends how you manage it

Maybe you can configure the oauth2 library? Or use another one...

Which Wilma version are you using? We introduce a patch that fix this issue few days ago. Please, could you update your code and try again?

Hi Michele,

many thanks for the report. It seems there is a problem in how PEP checks the requests. It should check only the resource and not the parameters. In your case it should check if the user has access to myResource, independently of the parameters. I will fix it ASAP.

BR

Hi,

many thanks for the report. As you can read, the vulnerability is related directly with the protocol and affects clients that are retrieving tokens from more than one AS. By the moment and until the working group proposes a fix, my recommendation is to follow the advise proposed there.

BR

Hi,

in Keyrock's documentatio you will find all the gran types accepted in OAuth2:

http://fiware-idm.readthedocs.org/en/...

You will find a lot of tutorials of how to use OAuth2 in Android applications over the internet. Keyrock fully implements the standard so it will be compatible with it (in fact other users are already using it with Android applications).

Don't hesitate to ask any other doubt.

BR

Hi,

are you using your own Keyrock instance or the official FIWARE Lab instance?

If you are using your own instance you have admin rights so you can use SCIM API to register users from your own server .

http://docs.keyrock.apiary.io/#refere...

If you are using the running instance in FIWARE Lab, the registration process must be done using its GUI.

Regarding the authentication, in both cases you can do the authentication directly from your side (and without the keyrock GUI) using Resource Owner Password Credentials Grant of OAuth2

http://fiware-idm.readthedocs.org/en/...

Hi,

if you refer to FIWARE Lab environment, the default token duration is 1 hour and cannot be modified. Of course you cannot obtain a token with unlimited expiration time due to security reasons.

If you instantiate your own Keyrock instance this parameter is configurable.

BR

We already support all the methods. Here is the updated documentation: http://fiware-idm.readthedocs.org/en/latest/oauth2/

Hi! There was an issue with some applications. We have just fixed the issue.

Many thanks for the feedback

Hi,

yes there is an API to validate OAuth2 tokens. In fact we provide a component that do the work of protecting your REST API using OAuth2 tokens. It si Wilma PEP Proxy:

http://catalogue.fiware.org/enablers/...

Regarding your second question, I guess I' already answered you via email :)

Hi Sam,

I don't fully understand your question. What do you mean with " But we wish to use the esource Owner Password Credentials Grant that keyrock allows to use."?

BR