You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the cmd doesn't present its credential on the secure channel, when polling until the project is accessible here.
This need to be changed, as a future change will prevent such connections to be established. The cmd always need to present its credential when establishing a secure channel to the project node. The places where we don't present credentials is when testing that the project' listener is accessible, in:
The project might is not yet stored at that point, if it was just created (for example after enroll), and is referenced through name instead of passing the project' data directly.
Right now the cmd doesn't present its credential on the secure channel, when polling until the project is accessible here.
This need to be changed, as a future change will prevent such connections to be established. The cmd always need to present its credential when establishing a secure channel to the project node. The places where we don't present credentials is when testing that the project' listener is accessible, in:
Unfortunately, it isn't as easy as setting credentials enabled here for a number of reasons:
InMemoryNode
after the project was created did not look promising (got error on0#ockam.ping.collector (origin: Node, kind: AlreadyExists,
, that indicate there are assumptions we broke if instantiating a new InMemoryNode). Changing it after the node was created seems possible? but I also failed on that attempt so letting it here for someone with more background on this to take over.The text was updated successfully, but these errors were encountered: