cancel
Showing results for 
Search instead for 
Did you mean: 
Create a Post

Starting New Sessions

Jump to solution

How can I start a new session without publishing the old one?

0 Kudos
1 Solution

Accepted Solutions

Re: Starting New Sessions

Jump to solution

The SmartConsole GUI allows one session per admin.

This means that you cannot create a new SmartConsole session without publishing/discarding your existing session first.

We have received requests from customers asking us to allow admins to have multiple sessions and to be able to work on each session independently and we have added this feature to our road-map.

In the meanwhile, it is worth mentioning that even through an admin cannot start a new SmartConsole session without publishing his previous session first, when it comes to working with the management APIs and not the SmartConsole GUI – the behavior is different:

  • When you log-in using the management APIs a new session is created and multiple concurrent sessions per admin are allowed.
  • This allows each script to run independently and to publish the changes that were created only by the script. In other words having each login command create a new session brings confidence that your script will not accidentally publish changes that were created by other scripts or SmartConsole sessions.
  • In case you do want the login command to continue your last session instead of creating a new session, add the “continue-last-session true” parameter to the login command. See documentation here.
  • If you want to start a session using the management APIs and later continue working on this session using SmartConsole – use the switch session API.
1 Reply

Re: Starting New Sessions

Jump to solution

The SmartConsole GUI allows one session per admin.

This means that you cannot create a new SmartConsole session without publishing/discarding your existing session first.

We have received requests from customers asking us to allow admins to have multiple sessions and to be able to work on each session independently and we have added this feature to our road-map.

In the meanwhile, it is worth mentioning that even through an admin cannot start a new SmartConsole session without publishing his previous session first, when it comes to working with the management APIs and not the SmartConsole GUI – the behavior is different:

  • When you log-in using the management APIs a new session is created and multiple concurrent sessions per admin are allowed.
  • This allows each script to run independently and to publish the changes that were created only by the script. In other words having each login command create a new session brings confidence that your script will not accidentally publish changes that were created by other scripts or SmartConsole sessions.
  • In case you do want the login command to continue your last session instead of creating a new session, add the “continue-last-session true” parameter to the login command. See documentation here.
  • If you want to start a session using the management APIs and later continue working on this session using SmartConsole – use the switch session API.