Latest Contributions by BrianLeroux

Hi All- I have a new Portal configure d and I am trying to get my first WAB app working properly. It seems that when I open the app it requests a token but only gets a 30 minute token. Once that expires the secured layer in my map stop functioning and no request for an updated token is ever requested. I then have to refresh the map every 30 minutes to keep things functioning. System cofig below. Let me know if anyone has any ideas. ArcGIS Enterprise 10.6.1 with Portal federated.  Secured with Windows Auth Web authenrtication Shortterm token set to 7,200 minutes (5 days) Long term tokens set for 7 days Thanks, ... View more

I am coming from an 10.1 server only system using Integrated windows Authentication. In that system users were automatically logged in with Windows credentials so it was invisible and seamless. Now I am standing up 10.6.1 with Portal Federated. We are still utiling our Integrated Windows Authentication. I am trying to wrap my head around correct settings and usage of tokens but have been struggling with understanding the following: 1.       Token Settings in Portal: maxTokenExpirationMinutes: -1  What does that setting apply to? Is that an application token? How does it relate to the server tokens below? All i read was that -1 means it is set for the maximum 2 week life. 2.       Token Settings in ArcGIS Server - Short and Long Life          What do these token settings apply to? Are these service tokens? Does portal handle requesting these as needed based on having authorized and app through the Idnetity Manager window? 3.       Identity Manager Token Validity          What does this property do? Does it related to an authorization token? Is that related to the setting in bullet 1 above but someone can use this setting to shorten the duration for a single app? 4.       oAuthInfo expiration          What does this property do? Is there any way to set things up so my users never need to go through an app authorization process. My users will not be utilizing the portal front end as my apps are typically embedded in our core systems. I appreciate any and all help. ... View more

I am moving from 10.1 to 10.6.1 and having some issues with SSO using active directory. For the 10.6.1 erver we are using Portal to handle security functions. It is using users and groups from AD. When I create a map that uses a secured service those layers do not load. There is an error in the web debugger regarding a token being needed. However on my old 10.1 server this was never an issue with the same map. I would see the first request fail and returns the negotiate package and the second request gets authorized. This is normal as described here. Windows Authentication HTTP Request Flow in IIS – Matt’s IIS Support Tidbits  The part I find strange is that if I navigate to Portal Home I get logged right in. Also if I go to a secure service  rest endpoint, I get logged right in. Once I go into either of those the layers in my map start working fine. When looking at the differences with the rest directory, On 10.1 the top right of the main rest directory screen shows my username logged in while on 10.6.1 there is a login button that I need to click. So It seems very strange that previously I never needed to do anything to log in but on this new 10.6.1 server I occasionally need to login by going to portal or a service before I can use my maps. This is going to be pretty confusing for the end users. Any ideas? ... View more