How to get an account with the FIWARE labs - fiware

I want to learn about FIWARE. I found out about FIWARE labs and tried to register in it. I was unable to register with them.
Unfortunately after repeted attempts, I was not able to register with the same. Everytime i would be getting a varification mail and every time as soon as i reply i would be getting the reply that that mail is held up for review. Can anyone help me on how to solve it.

Related

How long does google Take to review my Developer Console Project?

Problem In This
I am facing this problem.I once submitted my app for verification but after 2 weeks a mail came from google that we cant Verify your App/Project.There i used the "Icon" thats why they told me to verify.
Then i again created a new project,Do the same but didnt upload any icon.Simply go thorough the process.They showed "Verification Not required
Google hasent reviewed ur app yet..."
Its been more than 10 days, they didnt even reviewed it.
In this time what do i need to do?Wait for them untill they review my app,will it be ok if they review my app.
Or do i need to go through the verification process?But i dont have any scopes that required verification.Please suggest me what should i do.

Getting "Route not enabled for account" error while sending api activity request

When trying to getting response from https://developer.api.autodesk.com/bim360/admin/v1/projects/:projectId/activities it rises 403 error with details - Route not enabled for account. But, for example, request https://developer.api.autodesk.com/bim360/admin/v1/projects/:projectId/users has successfully responsed. User has all admin permissions.
Can every one help with that? :) Are there another ways to get project activities?
Unfortunately, activity API is not released yet, so you cannot use it currently. Please stay tuned with our official announcement in the further. Apologies for the inconvenience!

Fiware Keyrock - organizations are not returned AGAIN

I'm encountering the same problem asked here. The list of organizations of an authenticated user https://<idm_domain>/user?access_token=xxxxxxxxxxxxx is always empty.
I tried to follow the guide reported in the previous post to solve my problem but as reported in the past question, I can't find the button Authorize, the point 7 in the guide, so it's impossible to achieve.
Someone can help me!
Thanks in advance.
Did you solve the problem?
You can assign roles to users in organization directly from the dialog that appears when you press "manage" button. There you must assign some specific roles to the user, then you will see the organization in the list retrieved from the service.
If it does not work for you, just ask and we can continue working on it.

GCM: Subscribe Chrome extension to a topic

I'm currently trying to develop a Chrome extension which can receive notifications using GCM. When the extension is first installed, I register it using chrome.gcm.register(['my_sender_id'], function(registration_id) { console.log(registration_id); });.
I would like to send push messages to everyone who has the extension installed. However, the problem is that GCM requires you to specify the registration ID's of everyone you want to send the message to; you can't just send it to everyone who's connected to the sender ID.
While it would be possible to push the registration ID to a database when the extension is installed, and then consult this database each time I want to send a message, this solution seems sub-optimal (also from a security point of view, since the pushing of the registration ID would be done client-side).
However, Google introduced a solution for this a few years ago: topics. It's possible to simply register each device to a 'global' topic (for example) and when you then want to send a message, you only have to specify the 'global' topic as the receiver. However, I can't find how this registration process is done for Chrome extensions. I've looked everywhere, but it seems like Chrome's GCM module doesn't support this yet. Am I correct in this and if so, is there an alternative way to pull this off?
Any help would be greatly appreciated!
If you call chrome.instanceID.getToken and then use the InstanceID API from your server to subscribe to a topic, it seems to work, but then the chrome extension doesn't get messages when you push to that topic, so I'm not sure if Google just needs to enable something on their side to make it work. But this is the closest I could get to it in any case.
firebaser here
Thanks for the great feedback. There is no way at the moment to subscribe to a topic from a browser. We're aware that having such an API would simplify the development model. We'd love to add this to Firebase, but as usual can't make any promises or commitments.

Authentication token expiring within 10 seconds instead of 10 minutes

We currently have an implementation that uses boxes API. Our authentication process follows the process outlined here:
http://developers.box.com/get-started/#authenticating
Sometime in the recent past this has stopped working. When we go to the oauth URL (for example, https://www.box.net/api/1.0/auth/rev37d850p6pixlemm5ok8doxj2g77kg), it will initially show the login credentials page, but faster than a user could reasonably enter their credentials the page starts returning "expired ticket". If I immediately go to the token's page after creating it I can reload the page a few times before it goes into the "expired ticket" state. This is clearly not consistent with the expected 10 minute expiry time stated in the documentation.
We've had this authentication working correctly up to now, so it seems like something has changed.
We are investigating. More news once we have some additional information.
New info>> We've identified the bug, and will be pushing a fix this afternoon.
The fix has been rolled out. Please let us know if you are still experiencing any problems with SSO.
Our Android app has the same problem. As far as I investigated it, using get_auth_token API causes the ticket to expire. So you have to make sure the user has successfully logged in BEFORE attempting to get the authentication token (which is not the case with Box SDK for Android). But I don't see a viable way to check whether the user has logged in.