I have added a map to my portal, but it is continuously prompting for login.
I added it as a federated service to get around that, but for security reasons we need the two to be separated.
So now I am back to the webmap prompting for a log-in without the option to save credentials.
I have looked over a lot of older articles for a fix, but none of them seem they will work for me.
I have added the server where the map is as a "Trusted Server" in the portal settings, but still nothing.
Is there anyway to store the credentials so the webmap on portal acts as a public "face" for my service?
Thanks!
Hi Stephanie,
Lets start with the service.
1 - It is a non-federated server
2 - Yes, it is secured so I have to pass a token in to access the server
3 - I can access the rest service via browser once I log-in at the prompt provided.
If you add the service to Portal by going to My Content > Add Item > From the Web, are you asked whether or not to store your credentials?
That actually isn't showing up when I click add item. I'm going to clear my browser cache and restart my machine.
Okay, I had to change browsers for it to work. I was using firefox(up to date) and for some reason it would never pop up the "Store your credentials" dialogue. Thanks Jake!
I'm actually having a similar issue with login requests. We have a portal environment which we newly applied an Alias to (via bindings and our internal DNS). The alias works, but mysteriously asks for an additional login. Our regular named service does not do this. Is there anything I need to do on the portal side to allow the alias to function without the login request? I have already gone through the web adapters and configured them to also use the alias.
Appreciate any insight.