I accidentally executed the unregister API call on one of the five default sandbox accounts (username: sbMemXXX2, password: sbMemXXX2#123) when I was playing around with Test Drive. Attempting to log into it in Test Drive will return {"error":["Invalid User Credentials"]}. My other four sandbox accounts still work properly.
According to the docs, the register3 API functionality is disabled for the sandbox endpoint so I'm not sure how I can recover or remake this sandbox account. Does anyone know how to do this or do I need to contact Yodlee support?
Yes you are right, you won't be able to register a user in developer sandbox environment.
We recommend you to use the remaining 4 pre-provisioned user for testing purpose.
Hope this helps
Regards,
Krithik
Related
When I try to publish my app on the Gsuite Marketplace via GCP, I find no way to change the setting 'Visibility'. Event if the app has never been published.
Between the two options (My Domain - Public), My domain is selected and can't be switched to Public, so nobody has access to my app.
Any help?
I've tried to contact the support and find help on forums but no answer at all.
First step, I'd recommend reviewing Choosing where to publish to ensure that you've published to the correct location. As noted under Publish your app (before you publish), your app is reviewed to determine if it meets the requirements for the relevant store. Additionally, your application may also have to undergo OAuth verification (I think this could be the problem) , and security assessment if it accesses user data, such as Gmail, Drive, Contacts, or Calendar
If your app is exempt from verification or if you've already undergone assessment and been approved, and your issue persists, I'd recommend contacting Marketplace Developer Support, via the below steps, who can assist you with your publishing issue.
Navigate to the new Developer Dashboard.
Click Contact Us.
The Developer Support contact us form is displayed.
I've tried to contact the support and find help on forums but no answer at all.
How did you contact Google Support? They have many teams and sometimes agents are not aware of the scope of support. Personally I would contact GCP Support first to verify your App in GCP, once they confirm everything is working from their end they need to route the case to GSuite with an Admin Console specialist to debug the problem
Is there a way to test with the Twilio Connect App? You can only authorize an app that is not a free trial account by logging in which authorizes the production account. You do not get a chance to authorize a test account. Because of that any calls you try to make with the Connect App test credentials fail because your test credentials are not authorized to use the other production account. Does anyone know of any workarounds for this?
Public Disclosure:
Never have I tried any of the two suggestions given by Twillio, neither have I tried to actually implement them in my account.
Option 1: Create A New Account - Stay In Trial:
You said:
"...You can only authorize an app that is not a free trial account by
logging in which authorizes the production account"
This negates a fully-written suggestion in Twillio's site. From Twillio's help-center:
Test credentials only provide a way for you to "pretend" sending a
message or making a phone call ... If you are looking for end-to-end
testing without being charged, we recommend that you create a separate
Twilio account and stay in the trial mode to take advantage of the
trial credits.
Option 2: Using Your Test Credentials In Production Enviroment:
You said:
"...Because of that any calls you try to make with the Connect App test
credentials fail because your test credentials are not authorized to
use the other production account"
This seems strange, as in production, your test credentials will work - although just for specific services. From Twillio's docs:
Supported Resources
Your test credentials can currently be used to interact with the
following three resources:
Buying phone numbers:
POST /2010-04-01/Accounts/{TestAccountSid}/IncomingPhoneNumbers
Sending SMS messages:
POST /2010-04-01/Accounts/{TestAccountSid}/Messages
Making calls:
POST /2010-04-01/Accounts/{TestAccountSid}/Calls
Requests to any other resource with test credentials will receive a 403 Forbidden
response. In the future, we may enable these resources for testing as
well.
Hope this helps a bit. Nevertheless, tell us what you came up with in your different trial and errors.
Good luck!
The answer is no you cannot. The account has to be authorized through the Connect App and Connect App will not authorize trial accounts. When it authorizes a non trial account, it creates a sub account for that account only viewed through their API. The Api does not return the Test Account Id for the sub account so there is no way to figure out what the Test Account SID would be.
Because the account you want to "test" with has to be a production account you will be charged. I talked to Twilio Support about this and they acknowledged what I ran into and gave me a credit to my account to play around with. I would not expect that for everyone but hopefully this will be resolved soon.
I am developing an app using VB.Net for accessing my GMail accounts. I was able to follow the steps given at .Net Quickstart and was able to able access one of my accounts. So whenever I run my app, it accesses my first gmail account automatically, which is fine. Now I would like to access my other gmail account using the same app. How to change the gmail account that is automatically accessed by my desktop app?
This is similar to this question, but I am not able to understand the answer provided there
Thanks in advance for your answers
Before using your app, you need to log out of the default gmail account (i.e., first gmail account in your case). So I think you need to log out from that first gmail account, then log in with the second gmail account and try to sign in from your app. Hope this helps!
Finally I found out where the authorization information is stored. It is stored in Environment.SpecialFolder.ApplicationData folder. A folder named Google.Apis.Auth is created under this folder and a new file with the authorization information is created under it (in my case it is C:\Users\myWindowsUserName\AppData\Roaming\Google.Apis.Auth). I deleted the file which was there, which had the token for my first gmail ID. When I ran my app again, it asked for user login and consent once again, at which point I provided details of my second gmail account. This pearl is available here
As part of our "off-boarding" process for employees leaving the company, as super admins we use the Google Apps Admin SDK Directory API to change the user's password so that they can no longer access their account. Then we log in to do a Google Takeout, reset passwords for their other accounts, etc.
However, we recently decided to enforce 2-Step Verification for all of our users. So now when we go to log in to their account, it sends a code to their phone.
Since 2-Step is enforced for their SubOrg, we can't even turn it off through the admin console. So all I can do now is to have the API move the user to a different SubOrg where the 2-Step enforcement setting is turned off, and then manually turn off 2-Step.
Is there any way to programmatically turn off 2-Step verification for an account?
I looked in the Google Apps Admin SDK Directory API Users:update documentation, but it doesn't seem to have anything to do with 2-Step.
The Reports API can find out the user's enrollment status, but it's read-only for reporting purposes.
What you are doing is the correct way to remove the 2-Step verification. As you mentioned if it is enforced under a Organization Unit, removing it would get against that rule and that's why you are not able to do it unless you move the user to another OU where this is not enforced.
I was not able to find some way to do this programmatically. However, you could Suspend the user. After that, the user won't be able to access to that account. The account will still be visible in your Admin Console and all the information in the different Google services will remain attached to that account until you finally delete the account.
While the user is suspended, as admin, you can use service account to impersonate that user. By doing so you can act as that user and edit permissions or transfer the ownership of the files contained in Drive to a different account so those files won't get lost.
I hope this helps.
The easiest way to do this is to create a Group for which 2FA is exempt (see here: https://support.google.com/a/answer/2370108). Then add the user to that group, then you can click "Disable 2FA" on the user page in the admin console. I'm assuming you can do the same through the API.
The only downside is that this means you'll have a group through which it is possible to exempt users from the 2FA enforcement option. So that's a risk you'll have to accept and a policy you have to carefully check.
I've recently been doing a bit of web development so I've been thinking more about authentication and stuff. On Netflix I noticed there is an extra option on the Account page to de-authorize other devices. My girlfriend changed her password but I was still able to use it without re-entering the password till she logged out other devices.
So my question is how does authentication for Netflix work if it doesn't have to locally store your password?
Netflix uses a version of Open autentication to allow a device to access an account. Once the device has been authorized it will then have access to that account until its has been deautorized.
Chaning password doesnt matter becouse the device has autorization already probably in the form of a refresh token stored someplace. So its not storing a password its storing an autorization token of some kind.
Lets use facebook as an example: (response to comment below)
https://www.facebook.com/settings?tab=applications
This shows a list of all the crap I have loged in to using my facebook account. Now I have probably changed my facebook password sevral times it wont matter I will still have access. Some of these are mobil apps i have installed on my cellphone at one time or another. Even if i dont use them they still have access.
This doesn't technically answer the question, but is related and, I think, helpful:
You can forcefully invalidate the previously-validated tokens for other devices by going to https://www.netflix.com/ManageDevices - as soon as you go to the page it will ask if you want to sign out other devices.
(from "Someone is using my Netflix account without my permission" at https://help.netflix.com/en/node/18)