Boundary targets authorize-session with scope-names?

Boundary
1

Would anyone know why the “boundary targets authorize-session” doesn’t work with scope-names?
$ boundary targets authorize-session -name=testhost123 -scope-name=projectx
{“error”:“Error trying to authorize-session a session against target: empty targetId value and no combination of target name and scope ID/name passed into AuthorizeSession request”}

But it works if scope-id is used instead of scope-name:
$ boundary targets authorize-session -name=testhost123 -scope-id=p_xxxxxxx

And “boundary connect” using target-name and target-scope-name also works:
$ boundary connect http -target-name=testhost123 -target-scope-name=projectx

2

Hey @hannu.martikka,

Thanks for providing us feedback!

This issue with boundary targets authorize-session using scope-name has been identified and resolved. The fix will be available in the next release. For now, please use scope-id as a workaround.

2 Likes