fiware - Configuration Wilma Pep proxy 4.3 - Keyrock 4.3 local instance - IDAS -

we have installed keyrock instance (horizon + keystone) through automated tools in local enviroment (ubuntu 14.0.4 lts). have followed guide

keystone host: ubuntuhost keystone port: 5000

horizon host: ubuntuhost horizon port: 8000

we have installed pep proxy wilma in local enviroment (centos 6.6):

pep proxy wilma host: centoshost pep proxy wilma port: 80800

we want configure pep proxy wilma attack instance of idas installed in same enviroment pep proxy wilma:

idas host: centoshost idas port: 8080

in order have put following configuration file of pep proxy wilma:

config.account_host = 'ubuntuhost:8000';

config.keystone_host = 'ubuntuhost'; config.keystone_port = 5000;

config.app_host = 'centoshost'; config.app_port = '8080';

config.username = 'idm'; config.password = 'idm';

// in seconds config.chache_time = 300;

when try run pep proxy wilma server, following error shows up:

express deprecated app.configure: check app.get('env') in if statement server.js:35:5 starting pep proxy in port 80800. keystone authentication ... error in keystone communication {"error": {"message": "the request have made requires authentication.", "code": 401, "title": "unauthorized"}}

we not know happening here; if has horizon or keystone, or both of them

could this?

thanks in advance, rafa.

there can several reasons why failing think simple issue pep proxy user doesn't exists in keystone or not authorized.

in configuration file (config.js) of pep proxy should have 2 lines following:

config.username = 'pepproxy'; config.password = 'pepproxy'; 

there has user created in keystone back-end pep proxy, same way openstack services nova or glance have theirs.

if have used automated tools, can create user , authorize easily:

$ fab localhost keystone.console >>> pep = keystone.users.create(name='pepproxy', password='pepproxy', domain='default') >>> service_role = keystone.roles.find(name='service') # create if not found >>> keystone.roles.grant(role=role, user=pep, domain='default') 

you can operations using curl directly if feel more comfortable it. can find rest api documented here keystone identity api v3

as said, there can other causes why happening, please let me know if answer doesn't fix issue.