Difference between revisions of "GOCDB/notifications"
< GOCDB
Jump to navigation
Jump to search
Line 5: | Line 5: | ||
== Proposed Changes == | == Proposed Changes == | ||
Please contact [mailto:gocdb-admins@mailman.egi.eu gocdb-admins] if the changes listed below will have repercussions. | Please contact [mailto:gocdb-admins@mailman.egi.eu gocdb-admins] if the changes listed below will have repercussions. | ||
These changes were proposed at the Jan OMB with no objections | These changes were proposed at the Jan OMB with no objections: https://indico.egi.eu/indico/conferenceDisplay.py?confId=2372 | ||
https://indico.egi.eu/indico/conferenceDisplay.py?confId=2372 | |||
Plan to deploy on Tues 3rd March. | |||
=== UTF-8 Character Support === | === UTF-8 Character Support === | ||
Line 20: | Line 21: | ||
Sample changes highlighted below: | Sample changes highlighted below: | ||
[[File:GetUserXmlUpdates.jpg|400px|thumb| | [[File:GetUserXmlUpdates.jpg|400px|thumb|center|sample PI output with updates]] | ||
https://wiki.egi.eu/wiki/GOCDB/PI/get_user_method | https://wiki.egi.eu/wiki/GOCDB/PI/get_user_method | ||
<br/> | |||
<br/> | |||
=== Login via EGI SSO Username/Password === | |||
* Note, to login via EGI SSO, your account must already be associated with a valid/recognissed certificate (GOCDB will request SAML attribute for the user’s DN to map to an existing Gocdb account) | |||
* Allows login from browser without personal cert | |||
* Does not affect PI - x509 still required for protected methods (no SSO/SAML redirects) |
Revision as of 15:34, 11 February 2015
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Tools menu: | • Main page | • Instructions for developers | • AAI Proxy | • Accounting Portal | • Accounting Repository | • AppDB | • ARGO | • GGUS | • GOCDB |
• Message brokers | • Licenses | • OTAGs | • Operations Portal | • Perun | • EGI Collaboration tools | • LToS | • EGI Workload Manager |
Proposed Changes
Please contact gocdb-admins if the changes listed below will have repercussions. These changes were proposed at the Jan OMB with no objections: https://indico.egi.eu/indico/conferenceDisplay.py?confId=2372
Plan to deploy on Tues 3rd March.
UTF-8 Character Support
Allow UTF-8 characters for selected fields with rendering in the output of the relevant PI methods. This will allow chars such as àšëÂÒÚÿaúø (this is only a small selection). Initially allow for selected fields (can extend support to other fields later if required):
- Human readable Description fields on: Project, NGI, Site, Service, Service Group, Downtime, ServiceType.
- Extension Property values (Sites, Services, ServiceEndpoints, ServiceGroups).
get_user PI method updates
- New elements to be added: <SSOUSERNAME> and <PRIMARY_KEY> (PK of role's target entity)
- Update values of <ENTITY_TYPE> element so that:
- 'group' value is separated into 'ngi' and 'project'
- All values then become: project, ngi, site, servicegroup
Sample changes highlighted below:
https://wiki.egi.eu/wiki/GOCDB/PI/get_user_method
Login via EGI SSO Username/Password
- Note, to login via EGI SSO, your account must already be associated with a valid/recognissed certificate (GOCDB will request SAML attribute for the user’s DN to map to an existing Gocdb account)
- Allows login from browser without personal cert
- Does not affect PI - x509 still required for protected methods (no SSO/SAML redirects)