Currently, every plan I run through BlueAPI I need to specify a session to run it under. When I'm opening a run this makes sense as it will dictate where the data will be written to etc. but it doesn't make sense for actions such as doing a single move or doing a stop all as described in #1681.
This should not have any auth/auth concerns as we should be doing auth based on the user's token being authorised to use the beamline, not compared to the session that they specify (which they could easily spoof)
Acceptance Criteria
- I only need to provide a session for plans that open a run
Currently, every plan I run through BlueAPI I need to specify a session to run it under. When I'm opening a run this makes sense as it will dictate where the data will be written to etc. but it doesn't make sense for actions such as doing a single move or doing a stop all as described in #1681.
This should not have any auth/auth concerns as we should be doing auth based on the user's token being authorised to use the beamline, not compared to the session that they specify (which they could easily spoof)
Acceptance Criteria