Hi alvaro, I am not sure whom to direct this question, but I guess you may be the right person as it is related to the IDM somehow.

Please let me know if I should contact anyone else.

Thanks in advance for your help.

ilknur

Hi, he should view all the available projects in the "Project" selector of https://cloud.lab.fiware.org

BR

Dear Alvaro,

We just checked, we still seem to have an issue. To be more concrete, here is our specific case:

1- I have a community accouınt with user name ilknur chulani. My colleagues Burak and Omer were part of this community account.

2- My colleague Omer recently got another community account, and he can see both my cloud and his cloud by switching projects, without problems.

3 - Another colleague Burak also recently got a community account for another project, and added Omer and me. But now both Omer and I can not see his project in the project selector.

To be able to understand the root of the issue, the main difference between step 2 and 3 is the following:
In step 2, Omer was already part of my community account when he got his new one, but in Step 3 Burak tried to add us to his new community account while we already had accounts of own. normally this should not be an issue, but perhaps does IDM treat the two cases differently?

We are not sure how to proceed. It's important for us to access each other' s community accounts, since we are working on these three projects together.

Many thanks in advance for your help.

ilknur

Hi,

in third case, has he added your accounts correctly? You have to follow the steps in:

http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Lab:_Upgrade_to_Community_Account#How_can_authorize_other_users_to_use_my_cloud_resources.3F

Please, check that he has not omitted any step.

BR

Dear Alvaro,

We are having such a hard time to do the last step, i.e. "authorize". The screenshots and steps in the wiki page does not match the current version in the Cloud portal.

It is almost impossible to find the button for authorizing a member in the cloud organization, could you kindly point to the steps we need to follow in the new version, and update the wiki page as well?

I am sure other users are having a hard time as well!

Thanks in advance,

ilknur
Bu mesaj ve ekleri gönderilen kişiye özeldir ve gizli bilgiler içerebilir. Eğer mesajın gönderilmek istendiği kişi değilseniz lütfen kopyalamayınız, başkalarına göndermeyiniz ve göndericiyi bilgilendiriniz. Internet üzerinden gönderilen mesajların güvenli ve hatasız olduğunun garantisi olmadığından Atos grubu mesajın içeriğinden sorumlu tutulamaz. Göndericinin bilgisayarı anti-virüs sistemleri tarafından taranmaktadır, ancak yine de mesajın virüs içermediği garanti edilemez ve gönderici, meydana gelebilecek zararlardan sorumlu tutulamaz.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Dear Alvaro,

We managed to find the "authorize" button, and complete the steps. Did you update anything in the portal today? If you did, thank you very much.

If you haven't made any changes, it is still a mystery why sometimes the "authorize" button appears next to the manage button and sometimes not Any ideas?

Thanks again,

ilknur
Bu mesaj ve ekleri gönderilen kişiye özeldir ve gizli bilgiler içerebilir. Eğer mesajın gönderilmek istendiği kişi değilseniz lütfen kopyalamayınız, başkalarına göndermeyiniz ve göndericiyi bilgilendiriniz. Internet üzerinden gönderilen mesajların güvenli ve hatasız olduğunun garantisi olmadığından Atos grubu mesajın içeriğinden sorumlu tutulamaz. Göndericinin bilgisayarı anti-virüs sistemleri tarafından taranmaktadır, ancak yine de mesajın virüs içermediği garanti edilemez ve gönderici, meydana gelebilecek zararlardan sorumlu tutulamaz.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

If you are logged in as the organization (you have switched to it using the session button in the corner) and you are the owner you can manage the authorization.

Hi Alvaro,

Yes,we finally figured that out last week. You can close the ticket.

Thanks for your help,

ilknur