I have deployed a new Wirecloud instance (version 0.7) to a VM. Since, I registered it in the FI-WARE portal, I modified the Django settings in order to use the public IDM GE for security (authentication issues etc).
However, I get the message "Not Found 404. The resource you were looking for doesn't exist" during the Sign in process.
Given that the endpoinds of the IDM GE recently was modified, what about the integration between IDM and Wirecloud (urls, callback urls etc)?
Thank you
You need to upgrade your instance of WireCloud to version 0.7.2, as the support for KeyRock v2.0 was added in that version.
Related
I've correctly installed a Wirecloud instance in my own server. I've added a Marketplace available at this address http://130.206.81.113/FiwareMarketplace/v1.
I can retrieve the data from Marketplace correctly, and I can see all available widgets but I can't install anyone of them.
The only button present on each widget is Details, but I need Install to use them in my workspace.
Can I solve this issue in any way?
Thanks in advance.
Currently, WireCloud only allows you to install components from a marketplace/store if you are using the same IdM server in all the services: the marketplace, the store and WireCloud. As you want to use the global instance of the Marketplace, you should use the FIWARE Lab's KeyRock instance (https://account.lab.fiware.org) for authenticating users in your WireCloud instance to be able to install components from the FIWARE Lab's Marketplace.
NOTE: The Marketplace GE and the Store GE are currently in support mode. The Business API Ecosystem GE is going to replace it, but it won't be released until summer 2016.
We want to use the FIWARE IdM, both Keystone and Horizon. Specifically during sign-up we want to
create a user
add that user to an organisation
authorise the user for an application
We have installed Keystone and Horizon using the latest KeyRock docker image on the docker hub.
When a new user signs up:
a 'cloud organisation' is created.
By default, the 'provider' and 'purchaser' roles are present
and the 'Store' application is assigned to the user (although i cannot verify this).
We can add the user to an organisation by hand, and authorise the user for an application by hand in the KeyRock UI.
However this does not make any sense for our local installation.
How can we prevent Horizon from creating the cloud organisation upon user sign-up?
How can we assign a default application authorization upon user sign-up?
-- Edit --
It’s becoming increasingly clear to me that the way KeyRock is implemented is primarily useful for setting up your own Fiware labs environment, as opposed to setting up a generic Identity management service. If we use KeyRock, we will be stuck with cloud organisations, stores etc. Far from being a Generic Enabler (GE), KeyRock seems to be a “Fiware Labs” specific enabler.
All the GE documentation references KeyRock as the reference Identity Management GE. Therefore we (and i assume others too) have followed the documented architecture and configuration to link to KeyRock from:
Wilma PEP Proxy GE
Wirecloud Application Mashup GE
Because of the inbuilt Fiware Labs functions of KeyRock, we are having a really hard time applying Wilma PEP Proxy and Wirecloud Application Mashup to our use cases.
If we decide to use Keystone instead, we will lose
OAuth2 support
Permissions
sign-up, admin and login screens.
Is anyone else having this problem?
How have they tackled it?
-- SCIM API --
Attempt at using the SCIM API is described here: Fiware KeyRock SCIM API bug: _check_allowed_to_get_and_assign() got an unexpected keyword argument 'userName'
To use keyrock identity management need to install keystone in order to get authentication? and how to get single user value by using Get/Users/:id.
By installing oauth and node server.js i can able to login to my fiware login and get the access token this is a correct way for keyrock management implementation in web application.Kindly give guidance for implementation of keystone.
We are installing a Fiware enviroment in a local machine; we pretend to have an orion context broker with a Keyrock idm instance. We understand that we need to use a Pep Proxy in order to check the tokens of the requests to the orion context broker.
As we use Keyrock idm, we are wondering whether we have to install the keystone proxy or not. Is there any way to use them now without installing anything else or we are supposed to install the keystone proxy too?
This is the keystone proxy that we have found:
https://github.com/ging/fi-ware-keystone-proxy
If this is the case; How do we have to configure the pep proxy? Where do we have to put the data to connect to the Keyrock idm and where are we supposed to indicate the keystone information?
we have ready the new release of the Keyrock GE. With this new release Keystone Proxy will not be necessary anymore. We will publish the new documentation in a few days so please, I recommend you to use the new release.
BR
Using CAS 4.0.1 and successfully build with maven cas webapp and cas management app.
Accessing the cas-management app shows the services gui with the following error:
"The CAS management webapp is Unavailable
There was an error trying to complete your request. Please notify your support desk or try again."
I am able to solve my problem and I hope it might help you as well.
The reason behind this error is the security certificate was not in the VM parameter for my CAS server, namely
-Djavax.net.ssl.trustStore=truststore -Djavax.net.ssl.trustStorePassword=trustword"
If the CAS server has both cas and cas-management, then it requires the client certificate of this server to be part of the VM param.
The link http://docs.oracle.com/javase/7/docs/technotes/guides/security/jsse/JSSERefGuide.html#CreateKeystore shows how to create server and client certificates.