RHCLOUD-30751 Principal links endpoint update

[EvanCasey13]

Link(s) to Jira

https://issues.redhat.com/browse/RHCLOUD-30751

Description of Intent of Change(s)

Incorrect response when sending a request to principals endpoint for links, last should not be null.

"links": {
    "first": "/api/rbac/v1/principals/?limit=2&offset=0",
    "next": "/api/rbac/v1/principals/?limit=2&offset=36",
    "previous": "/api/rbac/v1/principals/?limit=2&offset=32",
    "last": null
  },

Changed from last:null to
"last": f"{path}?limit={limit}&offset={last_link_offset}{usernames_filter}",

Local Testing

How can the feature be exercised?
Run this curl command when running RBAC locally

curl -v "http://localhost:8000/api/rbac/v1/principals/" -H "accept: application/json"

How can the bug be exploited and fix confirmed?
Is any special local setup required?

Checklist

• if API spec changes are required, is the spec updated?
• are there any pre/post merge actions required? if so, document here.
• are theses changes covered by unit tests?
• if warranted, are documentation changes accounted for?
• does this require migration changes?
  • if yes, are they backwards compatible?
• is there known, direct impact to dependent teams/components?
  • if yes, how will this be handled?

Secure Coding Practices Checklist Link

• https://github.com/RedHatInsights/secure-coding-checklist

Secure Coding Practices Checklist

• Input Validation
• Output Encoding
• Authentication and Password Management
• Session Management
• Access Control
• Cryptographic Practices
• Error Handling and Logging
• Data Protection
• Communication Security
• System Configuration
• Database Security
• File Management
• Memory Management
• General Coding Practices

[petracihalova]

LGTM, I have only few tiny comments