-
Notifications
You must be signed in to change notification settings - Fork 531
Proper detection of IP addresses in JSF context #3103
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
Conversation
|
Michael, datasets and files are still not working and cannot assign ip groups to explicit groups. I've updated the original ticket. |
|
@michbarsinai heads up that this pull request now has conflicts that must be resolved before it can be merged. |
|
@michbarsinai , I am able to assign a member role to ipGroup3, all addresses, but cannot navigate directly to an unpublished dv. It does appear in the UI and API as a role assignment. Passing back for comment. |
|
This came up in the 8/2 Community Call (https://docs.google.com/document/d/1FsXatbbq-F4qwD_w9dqkFXpr2Sd4MqScKevUcHLCVDY/edit). |
…oup-localhost.json)
… a range (solves #3340)
Fix DataONE Maven URL. Conflicts: pom.xml
|
I just merged the latest from "develop" into this pull request: 00decd4 |
In a refactoring at c10cbd9 we lost the meaning of 0.0.0.0 which was "Setting address to undefined (0.0.0.0)" so this commit makes the code clearer. A note has been added that Saved Search may not play nicely with IP Groups but this should probably be addressed along with the long list of other Saved Search issues mentioned in the API Guide: #1364, #1813, #1840, #1890, #1939, #2167, #2186, #2053 and #2543
Conflicts: src/main/java/edu/harvard/iq/dataverse/api/BuiltinUsers.java src/main/java/edu/harvard/iq/dataverse/authorization/groups/impl/ipaddre ss/IpGroup.java src/main/java/edu/harvard/iq/dataverse/authorization/users/Authenticated User.java
RFI Checklist
Before submitting the pull request, fill out sections (1.) Related Issues and (2.) Pull Request Checklist.
1. Related Issues
2. Pull Request Checklist
3. Review Checklist
After the pull request has been submitted, fill out this section.
Connects to #3376.