OAUTH_APP_BLOCKED 'Developer' field in user story record is blank after successful sync external user stories Data Step with Related Records Data Deployment Error: INVALID_CROSS_REFERENCE_KEY : Record Type ID
Feb 23, 2017 · params is an associative array containing all the non oauth related parameters for this call. When I use this signed url I get an "invalid/used nonce" The OAuth Testing Tool uses the same OAuthSimple library and if I put in all the same parameters (including the timestamp) it generates exactly the same url.
Aug 06, 2012 · The 1.0 spec states: 3.3. Nonce and Timestamp. The timestamp value MUST be a positive integer. Unless otherwise specified by the server's documentation, the timestamp is expressed in the number of seconds since January 1, 1970 00:00:00 GMT. A nonce is a random string, uniquely generated by the client to allow the server to verify that a request ...
May 08, 2019 · A nonce is a random, unique value generated for each login attempt in certain login flows. If the same nonce is presented more than once, this security measure blocks the login attempt. The most likely scenario in your case is a logic bug in your code, possibly because of an interrupted connection attempt, where the app tries to reuse the ...
Had the same thing for a while -- I have yet to get loadDiscoveryDocumentAndTryLogin to work. Looking at the code, looks like it should work like a charm, but instead I had to revert to keeping them separate, also adding a bypass when you currently have a valid token
try using authconfig (oauthService.configure (authConfig)), instead of oauthservice properties.
Hmm, this seems pretty weird to me. If you only call loadDiscoveryDocumentAndTryLogin then only " try Login" is called, which does not actually send you to the IDS, but just tries to grab the details from the URL (nonce, tokens, etc). If you open the app the second time, the URL should contain none of those details.
Since things went quiet since last September, I'm hoping/assuming that you resolved things in the mean time. Let us know if you have additional details and we should reopen the issue!
We're also getting this error every now and then. We have noticed at least while using Angular 9, but we may have had the issue in A8 as well. Can't really pinpoint when it happens, it seems sort of random.
I got this when I accidentally left a call to oauthService.logOut in the constructor of my app component.
I am also facing this issue with v9.2.2 and Angular V9 very randomly. Can anyone suggest a fix for this issue