-
Notifications
You must be signed in to change notification settings - Fork 672
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
Now allowing Authsources to set validUntil and cacheDuration for Metadata. #1481
base: master
Are you sure you want to change the base?
Conversation
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.
Needs to be changed according to the (later) changes to the SP metadata refactoring + unit test update so we keep coverage of the new code up to date.
if ($metadata['expire'] - time() < $this->maxDuration) { | ||
$this->maxDuration = $metadata['expire'] - time(); | ||
if ($metadata['expire'] - time() < $this->cacheDuration) { | ||
$this->cacheDuration = $metadata['expire'] - time(); |
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.
I don't understand what this code wants to achieve. There is an expiration in the metadata. So we whould likely set validUntil to that value I think? Not cacheDuration? In any case the docs should probably say how the option interacts with expire
.
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.
Agreed.. I think it's also the wrong setting being set here.. Our metadata-converter converts validUntil to expire
.
I think it makes sense to drop the expire
-option in favour of validUntil
.
a96e0bf
to
575b81d
Compare
575b81d
to
ec3e5ec
Compare
Codecov Report
@@ Coverage Diff @@
## master #1481 +/- ##
=========================================
Coverage 40.05% 40.05%
- Complexity 3531 3532 +1
=========================================
Files 141 141
Lines 10596 10598 +2
=========================================
+ Hits 4244 4245 +1
- Misses 6352 6353 +1 |
I've rebased against |
There's still quite a lot of code that refers to expire when talking about remote entities I think. Are you referring to that or to the setting for hosted entities (does that exist?). |
It does not exist for hosted entities I think, so for remote entities... |
7a53fc8
to
d73ae47
Compare
e5c0e21
to
d5616df
Compare
2e6ab04
to
32f9acc
Compare
c743c9a
to
fc71570
Compare
29f7b69
to
1a911ce
Compare
c7c8357
to
fdbe001
Compare
3b5f5ba
to
96357ee
Compare
7587851
to
d523b31
Compare
8c90121
to
d534e3b
Compare
bc1c5c8
to
d0a5974
Compare
ccb9b02
to
120a100
Compare
6004a77
to
58bf8db
Compare
5c9fb2c
to
0970efc
Compare
Now allowing generation of SP metadata XML that includes @validuntil or @cacheDuration at EntityDescriptor.