Skip to content

Conversation

@ghost
Copy link

@ghost ghost commented Feb 2, 2022

The user who uses this package can decide if they want to make $spValidationOnly to be true

The user who uses this package can decide if they want to make `$spValidationOnly` to be true
@ghost
Copy link
Author

ghost commented Feb 2, 2022

I am very sorry I closed a pr, because I have never pushed a pr, this is my first ~

@ghost
Copy link
Author

ghost commented Feb 19, 2022

Is it convenient to ask what causes this PR not to be merged?

@ghost
Copy link
Author

ghost commented Feb 22, 2022

@pitbulk

* @throws OneLogin_Saml2_Error
*/
public function __construct($oldSettings = null)
public function __construct($oldSettings = null , $spValidationOnly = true)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From what I am seeing when looking at this, defaulting this to true will change the default functionality here, as before it would always be false. For backwards compatibility it would be best to set it to false

$settingsDir = TEST_ROOT .'/settings/';
include $settingsDir.'settings2.php';
unset($settingsInfo['idp']);
$settings = new OneLogin_Saml2_Settings($settingsInfo,true);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be good to have a test here that validates that errors are found when this is false, and the test that is defining the default value shouldn't pass it in as that will help verify that the default doesn't change.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, based on the error for the actions, it looks like the linter wants:

Suggested change
$settings = new OneLogin_Saml2_Settings($settingsInfo,true);
$settings = new OneLogin_Saml2_Settings($settingsInfo, true);

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for telling me don't forget format code, I have fixed them

@bzvestey
Copy link
Contributor

To merge this we just need to have the tests to pass, let me know if you are unable to view the details from the above actions that have failed.

@ghost
Copy link
Author

ghost commented Feb 25, 2022

Thanks for your concern. I have fixed the errors and push it again.

@ghost
Copy link
Author

ghost commented Feb 25, 2022

Hi , @bzvestey I can't know how to fix the error 'Could not validate timestamp: expired. Check system clock' , could you give me some help?

@bzvestey
Copy link
Contributor

I can try and take a look, but unfortunately I will not be able to do much time to until towards the end of next week.

@ghost
Copy link
Author

ghost commented Feb 25, 2022

I think it will take me some time. I will fix it try my best.

@ghost
Copy link
Author

ghost commented Feb 27, 2022

I have fixed it just now, I will push it as soon as possible, but I can't confirm if this repo master branch can run the tests passed, On my mac and my cloud server, it seems can't pass the tests. could you let me know the result of you running the test if it can be passed?

@bzvestey bzvestey merged commit 4f94a76 into SAML-Toolkits:master Feb 28, 2022
@bzvestey
Copy link
Contributor

Thank you for all of the time you put into this!

@ghost ghost mentioned this pull request Mar 1, 2022
@ghost ghost mentioned this pull request Jul 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants