-
Notifications
You must be signed in to change notification settings - Fork 546
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
Introduce JDBC based persistence for SAML #6294
base: master
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #6294 +/- ##
============================================
+ Coverage 45.96% 46.10% +0.13%
- Complexity 14586 14654 +68
============================================
Files 1662 1665 +3
Lines 104487 104818 +331
Branches 18354 18395 +41
============================================
+ Hits 48031 48327 +296
- Misses 49612 49615 +3
- Partials 6844 6876 +32
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
namedPreparedStatement -> namedPreparedStatement.setInt(TENANT_ID, tenantId)); | ||
|
||
for (SAMLSSOServiceProviderDO serviceProviderDO : serviceProvidersList) { | ||
addProperties(processGetServiceProviderId(serviceProviderDO.getIssuer(), tenantId), serviceProviderDO); |
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.
addProperties
-> populateProperties
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.
Can we populate this details executing only one query, rather executing many (=serviceProvidersList.size
)?
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.
addProperties
->populateProperties
changed in
Introduce JDBC based persistence for SAML
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.
Can we populate this details executing only one query, rather executing many (=
serviceProvidersList.size
)?
will work on it
PR builder started |
PR builder completed |
PR builder started |
PR builder completed |
@Osara-B shall we verify this test locally? |
6f25515
to
a433ef5
Compare
samlSSOServiceProviderManager.addServiceProvider(sampleServiceProvider1, TENANT_ID); | ||
assertTrue(samlSSOServiceProviderManager.removeServiceProvider(getIssuerWithQualifier(ISSUER1), TENANT_ID)); | ||
assertNull(samlSSOServiceProviderManager.getServiceProvider(getIssuerWithQualifier(ISSUER1), TENANT_ID)); | ||
|
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.
Let's remove the unwanted empty line
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.
resolved
|
||
lenient().when(dataSource.getConnection()).thenReturn(spyConnection); | ||
lenient().doNothing().when(spyConnection).close(); | ||
|
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.
Let's remove the unwanted empty line
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.
resolved in Introduce JDBC based persistence for SAML
a433ef5
to
7968925
Compare
Quality Gate passedIssues Measures |
Tests are passing locally |
Proposed changes in this pull request