Hi, me again. Little status update, have successfully rewritten the library work with the container, have couple of questions about structuring it and configuration. 1. Haven't got much experience with writing api libraries and managing expiring tokens. Should I need to worry about token expiring? I presume it is not needed to make a new authentification, everytime we interact with storage. The authentification should happen once when server is starting-up (we create a instance) and it internally keeps it. Should I implement some kind of mechanism that refreshes the token? 2. Does the tenant id change? From the quote below I presume that getting a tenant I just a one time deal. > A valid token is required to access an object store. This section > describes how to get a valid token assuming an identity management system > compatible with OpenStack Keystone is being used. If the username, password > and tenant details are known, only step 3 is required. source > <http://s.bl-1.com/h/vNCB1Mf?url=https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Object_Storage_-_User_and_Programmers_Guide#Authentication> > 3. From a response list of tenants (as shown in the picture below) how should I select the "right" one? For now i'm just taking the first one. [image: Inline images 1] 4. Is it true that a object storage container belongs to only a single region? Now when initiating the storage library the passed in config object requires an region key. For my trial account it's locked to Spain2. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-lab-help/attachments/20160119/3aa233fd/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2016-01-19 at 00.02.53.png Type: image/png Size: 133293 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-lab-help/attachments/20160119/3aa233fd/attachment.png>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy