Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Secure VRAConnect #227

Closed
martin9700 opened this issue Jun 29, 2020 · 5 comments
Closed

Secure VRAConnect #227

martin9700 opened this issue Jun 29, 2020 · 5 comments
Labels
Milestone

Comments

@martin9700
Copy link
Contributor

Steps to reproduce

$Global:vraconnection
Server : https://server.domain.local Token : <token> RefreshToken : <refreshtoken> APIVersion : 2019-01-15 SignedCertificates : False SslProtocol : Default

Expected behavior

$Global:vraconnection

Also: $Script:vraconnection

@Stevio54
Copy link
Contributor

Stevio54 commented Jul 1, 2020

could you detail out the issue please?

@martin9700
Copy link
Contributor Author

Sure, when you Connect-VraServer, you can simply type $Global:VraConnection and see both tokens required for accessing VRA. It would certainly be possible for someone to walk up , get those tokens then start doing work AS YOU. Attack surface area is pretty low, but it's simple to fix so why not?

I can submit a PR if you'd like?

@Stevio54
Copy link
Contributor

Stevio54 commented Jul 2, 2020

Thanks for clarifying the issue. Would it be possible for you to submit a PR?

@jonathanmedd
Copy link
Contributor

Thanks for this! I didn't realise until today that “script scope in a module is module scope” otherwise we would have done this from the beginning :-)

@martin9700
Copy link
Contributor Author

Right?! As soon as I read about it I switched all my modules to use that!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants