The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
GOCDB/notifications
< GOCDB
Jump to navigation
Jump to search
| 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 following updates 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) on the following fields:
- Human readable 'Description' fields for: Project, NGI, Site, Service, Service Group, Downtime, ServiceType, Scope.
- Certification status change 'Reason' field.
- User Forename and Surname (note, not Cert DN!)
- Extension Property values (Sites, Services, ServiceEndpoints, ServiceGroups).
get_user PI method updates
- PI method: https://wiki.egi.eu/wiki/GOCDB/PI/get_user_method
- 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:
Login via EGI SSO Username/Password
- Note, to login via EGI SSO, your account will need to 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 a browser without personal cert loaded in browser
- Does not affect PI - x509 still required for protected methods (no SSO/SAML redirects)