[Backlogmanager] [FIWARE-JIRA] (HELP-9377) [fiware-stackoverflow] Access Fiware objectstorage from Ruby: how do I connect without using password

[Fernando Lopez (JIRA)]

     [ https://jira.fiware.org/browse/HELP-9377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fernando Lopez deleted HELP-9377:
---------------------------------


> [fiware-stackoverflow] Access Fiware objectstorage from Ruby: how do I connect without using password
> -----------------------------------------------------------------------------------------------------
>
>                 Key: HELP-9377
>                 URL: https://jira.fiware.org/browse/HELP-9377
>             Project: Help-Desk
>          Issue Type: Monitor
>            Reporter: Backlog Manager
>              Labels: fiware, openstack-swift, ruby
>
> Created question in FIWARE Q/A platform on 24-07-2015 at 13:07
> {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/31609429/access-fiware-objectstorage-from-ruby-how-do-i-connect-without-using-password
> +Question:+
> Access Fiware objectstorage from Ruby: how do I connect without using password
> +Description:+
> I have an ruby-on-rails app which should store and retrieve images from Fiware objectstorage (which is based on Openstack swift).
> There is gem called ruby-openstack that semm to do everything I need. 
> It works when I hardcode my email and fiware-password. But this seem not to be the right thing to do. The connection method gives me two other options:
> # :auth_method - Type of authentication - 'password', 'key', 'rax-kskey' - defaults to 'password'"
> # :username - Your OpenStack username or public key, depending on auth_method. *required*
> # :api_key - Your OpenStack API key *required* (either private key or password, depending on auth_method)
> Should I choose "key" or "rax-kskey", and where do I get these keys from?
> Is the private key the same I use to log in via ssh? 
> Or has it something to do with the "app" I can create in the Fiware-Backend? 



--
This message was sent by Atlassian JIRA
(v6.4.1#64016)