-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[TACACS] Send remote address in TACACS+ authorization message. #12190
[TACACS] Send remote address in TACACS+ authorization message. #12190
Conversation
Will create E2E test case in sonic-mgmt repo with another PR. |
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
d030fcb
to
1c25f25
Compare
src/tacacs/nss/patch/0010-Send-remote-address-in-TACACS-authorization-message.patch
Outdated
Show resolved
Hide resolved
src/tacacs/nss/patch/0010-Send-remote-address-in-TACACS-authorization-message.patch
Outdated
Show resolved
Hide resolved
src/tacacs/nss/patch/0010-Send-remote-address-in-TACACS-authorization-message.patch
Outdated
Show resolved
Hide resolved
src/tacacs/nss/patch/0010-Send-remote-address-in-TACACS-authorization-message.patch
Outdated
Show resolved
Hide resolved
src/tacacs/nss/patch/0010-Send-remote-address-in-TACACS-authorization-message.patch
Outdated
Show resolved
Hide resolved
src/tacacs/nss/patch/0010-Send-remote-address-in-TACACS-authorization-message.patch
Outdated
Show resolved
Hide resolved
src/tacacs/nss/patch/0010-Send-remote-address-in-TACACS-authorization-message.patch
Outdated
Show resolved
Hide resolved
+/* | ||
+ * Get environment variable first part by name and delimiters | ||
+ */ | ||
+int get_environment_variable_first_part(char* dst, socklen_t size, const char* name, const char* delimiters) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed, add constants for return values.
Send remote address in TACACS+ authorization message. #### Why I did it TACACS+ authorization message not send remote address to server side. #### How I did it Send remote address in TACACS+ authorization message. #### How to verify it Pass all E2E test. Create new test case to validate remote address been send to server side. #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 201811 - [ ] 201911 - [ ] 202006 - [ ] 202012 - [ ] 202106 - [ ] 202111 - [ ] 202205 #### Description for the changelog Send remote address in TACACS+ authorization message. #### Ensure to add label/tag for the feature raised. example - [PR#2174](sonic-net/sonic-utilities#2174) where, Generic Config and Update feature has been labelled as GCU. #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> #### A picture of a cute animal (not mandatory but encouraged)
…7702) **What I did** Add UT to check TACACS will send remote address to server. **Why I did it** nss-tacplus add a patch to send remote address to server with this PR:sonic-net/sonic-buildimage#12190 To protect the patch, add this UT to check TACACS will send remote address to server. **How I verified it** Pass all UT.
Send remote address in TACACS+ authorization message.
Why I did it
TACACS+ authorization message not send remote address to server side.
How I did it
Send remote address in TACACS+ authorization message.
How to verify it
Pass all E2E test.
Create new test case to validate remote address been send to server side.
Which release branch to backport (provide reason below if selected)
Description for the changelog
Send remote address in TACACS+ authorization message.
Ensure to add label/tag for the feature raised. example - PR#2174 where, Generic Config and Update feature has been labelled as GCU.
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)