Anyone notice that you'll get a `INVALID_LOGIN_ATT...
# suitescript
d
Anyone notice that you'll get a
INVALID_LOGIN_ATTEMPT
in PostMan say 3 out of 10 attempts? Simply hitting send 'again' ensure it goes through ok. Is this expected?
s
Can't say I've seen that, but I've also recently been moving towards code-based integration tests rather than postman.
I have seen issues in postman seemingly not handling variable/environment settings for TBA auth properties
which in turn would cause INVALID_LOGIN - but that was consistent, not intermittent.
d
Right, ok. Its definitely intermittent. The live system we testing against also get intermittent
INVALID_LOGIN_ATTEMPT
I caulk it up to it being a TSTDRV account, but my client isn't buying it ... nearly impossible to figure out since there are plenty of successsful calls
I've seen a few posts claiming it had to do with server times not being in sync ... not sure how I can check that though
b
What does the login audit trail say
d
Just a
FAILURE
. However, the one consistency is .. the
FAILURE
lack a 'role'
I'd like to explore the timestamp differences between the 'sender' and 'netsuite'. I just don't know how to get NetSuite's server time
s
isn't
new Date()
server time on a backend script?
b
Are you saying the detail column has no value?
d
Oh! ... InvalidSignature
How can the programmatically generated signature be right only 80% of the time?
b
potentially a failure in the nonce
d
I think there's a specific failure message for nonce-rejected, Invalid timestamp
s
are you sending the exact same request and it fails intermittently?
d
Correct
The failure is always 'InvalidSignature'
s
I wonder if it's some sort of caching thing on the NS side? have you updated the token recently?
d
I'll say yes to that ... we tried to see if a fresh token would fix it .. no go
So, today, we've had 30 attempts ... 6 failed.
s
well if it was happening prior with a long standing token I don't suppose it could be any sort of out-of-date key stuff on the NS side.
d
of those 6 failures .. 4 were almost immediately on top of each other ... so perhaps TOO quick (and a timestamp issue)
s
and this is only via postman? do you have other clients (not postman) making connections without issues?
d
We saw it via PostMan during Dev and Unit testing ...
We're observing it again with Live Testing with the client
About the same frequency as well ... maybe its just an issue with our TSTDRV account
s
yeah, if you have two independent clients seeing that error you may be in NS Case territory
b
if you go to a netsuite support case
expect to be able to show that the signature generated is correct