You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If one programatically logs in as user 1 it will authorise and the content can be written to fedora. Though the issue here is that file_put_contents returns successful when it has in fact failed.
When does this issue occur?
N/A.
Which page does it occur on?
N/A.
What happens?
N/A.
To whom does it occur (anonymous visitor, editor, administrator)?
Users without permission to write to fedora.
What did you expect to happen?
That file_put_contents would return FALSE.
Which version of Islandora are you using?
2.2.0
Any related open or closed issues to this bug report?
No
Screenshots:
N/A.
The text was updated successfully, but these errors were encountered:
$code = $response->getStatusCode();
if (!in_array($code, [201, 204])) {
returnFALSE;
}
Someone is going to need to step through this with a debugger (or use a liberal amount of logging statements) to figure out how this is getting through.
What steps does it take to reproduce the issue?
Use the following command, on a working site.
Enter in the following code.
Note that it response successfully with
9
bytes written. However it did not actually write to fedora which can be confirmed with the following code.Which yields 'false'.
From the fedora logs we can see this failed to authorise with
403
as the returned status code on thePUT
request.If one programatically logs in as user 1 it will authorise and the content can be written to fedora. Though the issue here is that
file_put_contents
returns successful when it has in fact failed.N/A.
N/A.
N/A.
Users without permission to write to fedora.
That
file_put_contents
would returnFALSE
.Which version of Islandora are you using?
2.2.0
Any related open or closed issues to this bug report?
No
Screenshots:
N/A.
The text was updated successfully, but these errors were encountered: