Details
-
Type:
Feature Request
-
Status: RESOLVED
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 12.0
-
Fix Version/s: 12.0
-
Component/s: Internationalization, Web Services
-
Labels:None
-
Test Plan:
1. Clear your cached content in your browser and refresh.
2. Click on the login options top right, your user photo.
3. Click on 'My Connections'
4. In the connection manager, search for people by typing their names in the search box.
5. Send one a connection request.You should see the connection request appear in the Pending tab, with translations applied, 'Cancel Request' for instance. This shows that the connection manager code has successfully retrieved the strings from the i18n webservice and that all is well
1. Clear your cached content in your browser and refresh. 2. Click on the login options top right, your user photo. 3. Click on 'My Connections' 4. In the connection manager, search for people by typing their names in the search box. 5. Send one a connection request. You should see the connection request appear in the Pending tab, with translations applied, 'Cancel Request' for instance. This shows that the connection manager code has successfully retrieved the strings from the i18n webservice and that all is well
Description
Rather than having a config value with a default set of values to mark services as not having the standard IP restrictions I think it clearer to have an annotation to mark a service as non-restricted. This way it's clearer when looking at the code that the endpoint isn't IP restricted and it also means if someone develops a local WS that they don't want IP restricted they can mark it as such, without having to worry that they won't pickup upstream config changes for this property.
Gliffy Diagrams
Zeplin
Attachments
Issue Links
- is related to
-
SAK-32728 RemoteHostFilter should allow certain endpoints to work
-
- RESOLVED
-