Attempt to configure CA for insecure device during onboarding to cloud #198
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jkralik
force-pushed
the
jkralik/feature/insecure-device-set-ca
branch
from
b72206e
to
06e520a
Compare
jkralik
force-pushed
the
jkralik/feature/insecure-device-set-ca
branch
from
06e520a
to
795d579
Compare
jkralik
force-pushed
the
jkralik/feature/insecure-device-set-ca
branch
2 times, most recently
from
0ada73a
to
4da10a5
Compare
jkralik
changed the title
It is expected that the insecure device is within the trust network, and the client application is behind the proxy that authorizes access
jkralik
force-pushed
the
jkralik/feature/insecure-device-set-ca
branch
from
4da10a5
to
216f65f
Compare
|
Danielius1922
approved these changes
Feb 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For this use-case, it is expected that the insecure device is within the trust network,
and the client application is behind the proxy that authorizes access