Skip to main content
C
Clarke_Hair
May 27, 2025

Local User Access when SSO turned on or need to set WF for local user when you can't access user.

  • May 27, 2025
  • 3 replies
  • 0 views

in our initial design we have a local Admin user - OS_Admin that runs all our DM and Scheduler jobs. This was a local Admin user that pwd never changed (IT requires all AD users to change pwd's and we have too many embedded scripts with pwd for this to work).  When we migrated to V8 and the new SSO security structure was applied, we found that keeping the option for manual user sign-in created more issues for our SSO users than we could justify so we have stopped being able to sign in as this user.

Issue:  We have logic that is pointing to the Global and this user's settings that drive most of our activity.  In the short-term I have changed the User based settings to point to my user but I need to get away from that.

Need: I need to be able to sign-in as the local user to set the POV for WF (Scenario, Time, WF) OR is there a way I can change that from my Admin user.  Don't care either way, just need the result to be that the OS_Admin user's POV is updated. 

3 replies

T
TGG_Alex
May 28, 2025

Hi @Clarke,

To clarify, your OneStream application has logic that leverages the POV of a native user account called OS_Admin (e.g., Workflow POV and Cube POV) alongside the set Global POV?

Are you looking for a way to programmatically change the POV of the OS_Admin user's POV?  What issues were created after upgrade to OSS PV800+ for this user?

We have built logic that can change this but need to better understand your requirements before being able to determine if it can help your situation.

 

Cheers,

A.

 

 

 

C
Clarke_HairAuthor
May 30, 2025

pre-V8 the user's name could be retained so they did not have to enter it again each time they signed in.  Once we went to V8 there was a security change that now required users to enter their name each time they tried to sign in.  It was to burdensome for our users to keep both SSO and Native sign-in available so we turned off Native sign-in.  Now users are not required to enter anything when signing in.

Just need to update OS_Admin's POV so downstream logic can grab the correct Time, Scenario & WF.  These values are used in other processes.

My assumption is I can't sign-in since we have turned Native off so looking for a programmatic way to update this information.

R
RobbSalzmann
June 2, 2025

If the requirement is to store a set of values, Time, Scenario, and Workflow for other processes, this is the use case for Literal Parameters.
Create three Literal Parameters to hold these values
prm_OS_Admin_POV_Scenario
prm_OS_Admin_POV_Time
prm_OS_Admin_POV_Workflow

Now you can access these values from any business rule, assembly, or UI object without the need for a dedicated machine account to store a POV. 

Terms & ConditionsAccessibility statement