Cannot log in again. idpsso blocking.

[Pavel A.]

I am unable to log on to my ST account for two days. The community forum itself reads well, no delays etc.

But logging in fails because idpsso.st.com does not respond (browser reports timeout). From my location IP address of idpsso resolves to 164.130.1.34.

(Now I've logged in via a proxy with exit point with very good reputation in the USA, but cannot use it all the time).

Had tried to redirect either  idpsso.st.com or idsso.st.com, both seem to enable logging in.

[TDK]

Getting hit with the same thing here tonight. It force-logged me out and then wouldn't let me log in again.

I can log in with a VPN, sometimes. Cannot log in without it.

[Lina_DABASINSKAITE]

Hello @Pavel A. , @TDK 

I’m sorry to hear to you face these issues. We are looking into this and will let you know once I have news. 

Let me know if you notice any other nonstandard behavior. 

Thanks,
Lina

[Lina_DABASINSKAITE]

Hi @Pavel A.  and @TDK 

A couple of follow-up questions: 

1. Are you facing this issue with one specific browser or with multiple ones? Name the ones that you face issues with. 
2. @Pavel A. , are you able to connect using a VPN (similar to what TDK reported).

3. Have you both tired cleaning the browsers' cookies/cache files to see if it has any effect?

Thanks, 
Lina

[Tesla DeLorean]

Not had it lock me out, but the login-redirect honestly seems a tad more fragile within the last few days/week.

Using Windows PC w/Chrome, and Android. Couple of instances of Comcast at two locations, and off a Verizon based MVNO.

I think the login prompts populate before the entire page loads, and that can break the login/forward if clicked too quickly. Might want to review what scripts you're running, the amount of activity, and the amount of off-site linking.

[Andrew Neil]

I had this at the end of last week - discussed in PM with @Lina_DABASINSKAITE 

I found that using a different browser helped:

I normally use Chrome, and that suffered the problem, but I could log-in fine using Edge on the exact same computer on the exact same network.

Clearing cookies on Chrome made no difference.

 

(I've also been seeing that other thing where you get an error from the login, but the login was actually successful)

[Pavel A.]

The new Edge is a close relative of Chrome,  would be surprising if they behaved differently.

Today the IP address of idpsso has changed. so it looks that somebody are working on the issue )) Take your time guys, we'll wait. Hope this is not caused by yet another cable wreck.

 

[Andrew Neil]

---

@Pavel A. wrote:

The new Edge is a close relative of Chrome.

---

I know.

 

---

@Pavel A. wrote:

would be surprising if they behaved differently.

---

Indeed - I was surprised that they did behave differently!

[Pavel A.]

Today log-in works normally. Thanks.

@Andrew Neil  I've used only Edge on win11 on both machines (with VPN and without it) and it did not "work" without VPN. So not convinced about different browsers.

.........

Edit Dec. 24:

Spoiled! Yesterday idpsso timed out again. Posting this via the VPN again

[Tesla DeLorean]

Unable to login from Android/Chrome, just hangs up during the redirect (shows a few percent progress, doesn't get any further, and times out), other websites all working fine. Main site ok.

Site also fine from Windows/Chrome, from same network/wifi

[Tesla DeLorean]

Been persistently blocked on Android/Chrome this week. Just chokes on the address resolution

 

This site can’t be reached

The webpage at https://idpsso.st.com/idp/0b4yteOp8z/resumeSAML20/idp/SSO.ping might be temporarily down or it may have moved permanently to a new web address.

ERR_CONNECTION_ABORTED

[Tesla DeLorean]

Struggling a lot today on a Win11 PC w/Chrome.

It's like the redirect when repeated triggers some denial-of-service type lock-out so the failure cascades. Trying later got me a Page Not Found / HTTP ERROR 404 type response on the return leg. https://my.st.com/cas-idpwebsso/login?resume=...

This session, on a different PC and location, went via SSO.ST and succeeded first go around, so I see this as an issue that compounds itself. I don't understand why the authentication fails, it surely has to be filling up the logs with this non-sense.

[TDK]

Still happens occasionally to me. Losing interest in helping troubleshoot issues with basic functionality.

[Tesla DeLorean]

Yeah, it's got to be flagging up in the logs, and eating some bandwidth.

Feels like it's timing related, and overly complicated scripting and jumping back-n-forth between servers and authenticators.

But yes, not sure why we're having to debug this, or why the constant fiddling

[Laurids_PETERSEN]

Hello,
Sorry that the log in process still isn't working as intended. 

Here is an update: The root cause in the SSO is identified and a fix is in process.
I'll let you know again once completed.

Best regards,
Laurids

[Laurids_PETERSEN]

Hello everyone,

A fix has been deployed for this issue. To force it to work, please clear your browser cache.
If it's still not functional, please let me know in this thread.

Best regards,
Laurids

[TDK]

This is happening again, has been occurring all week. Clearing browser cache does nothing.

[Tesla DeLorean]

+1 Yes, been a bit inconsistent here too.

The login screen really needs to be decluttered, needs to stop off-site linking (resources, scripts), painting feed-back tabs, etc.

If I can auto-fill the fields and click-thru before the page fully renders, there's too much going on.

Get it working and quit fiddling with things