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.

Sign up for GitHub

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

Jump to bottom

feat: whether or not to handle (e.g. sending an event) themis auth failures (besides ignoring the failure) #49

Open
denopink opened this issue Mar 28, 2024 · 1 comment
Open

feat: whether or not to handle (e.g. sending an event) themis auth failures (besides ignoring the failure) #49

denopink opened this issue Mar 28, 2024 · 1 comment
Labels
enhancement improvement or small functionality added to an existing feature

Comments

@denopink
Copy link
Contributor

denopink commented Mar 28, 2024 •
edited
Loading

xmidt-agent/internal/websocket/ws.go

Lines 205 to 206 in 1b1515e

// If auth fails, then continue with openfail xmidt connection
ws.credDecorator(ws.additionalHeaders)

@denopink denopink added the enhancement improvement or small functionality added to an existing feature label Mar 28, 2024
@denopink denopink changed the title should there be a log or event sent when themis auth fails feat: should there be a log or event sent when themis auth fails Mar 28, 2024
@denopink denopink changed the title feat: should there be a log or event sent when themis auth fails feat: whether or not to handle (e.g. sending an event) themis auth failures (besides ignoring the failure) Apr 18, 2024
@denopink
Copy link
Contributor Author

related to #87 as the likely solution

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement improvement or small functionality added to an existing feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@denopink