Adding secure services as items not working

[AndrewSpencer]

The process as described in this blog: How To: Add Secure ArcGIS Server Services as Items in ArcGIS Online does not seem to be available anymore. Furthermore, our existing items that reference secure services no longer work. Is there a problem here, or has something changed in the last day or so?

[AndrewSpencer]

I've narrowed it down to shenanigans with certificates - nothing to do AGOL at all which is good to know. It appears our IT guys may be up to something, and, let's say, haven't quite ticked all the boxes. Thank you for helping with this.

[MichaelTorbett]

This is probably not related, but I've been having a similar issue for a about a year. We did an ArcGIS Enterprise migration from on-premise to Azure. Ever since then, I've been getting a message "invalid user name or password" when trying to embed credentials into Items added to ArcGIS Online that are hosted in our enterprise portal. What I discovered is now I have to be logged into VPN to be able to embed credentials into secured items. Otherwise ArcGIS Online can't reach our portal's authentication service. 

I think the reason for this is because when I did the migration, I was logged into VPN and it has somehow inserted itself into the fibers of ArcGIS Enterprise. I'm now looking at doing an uninstall/reinstall of ArcGIS Enterprise to try and fix this issue.

If certificates ends up not being the issue, then it might not hurt to take a look at VPN if you use it. 

Michael

[JudithCauldwell]

We've had the same trouble. Thought it was firewall but have proved it's not. I think it's been a problem since February 2025 here. Both US and EU hosted AGOL instances seem to have an issue. Unsecured services are fine.

I also suspect that the secured service caches a token somehow (so maybe gets a longer life token when it requests one, more than 1 hour that is) which is why people are experiencing issues with this at different times, but that's just a guess, I've no evidence just a gut feeling.

Should probably add that we're using a federated Enterprise instance, which does effect how secure services present when you go to add them in AGOL.