Custom Query (1408 matches)
Results (34 - 36 of 1408)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#1026 | fixed | getversion reports wrong ION URN | ||
Description |
In the GetVersion response from ION, the urn reported is:
That should be: |
|||
#1027 | fixed | use a cert with the correct URN | ||
Description |
PG cares that the ION AMs urn says 'ionpl+authority+sa' instead of 'ion.internet2.edu+authority+am' and wants this changed. Work on regenerating the correct self signed certificate and using that instead. Tony Mack says: You can use the following commands to regenerate your registry certs and maintain the existing keys: $ sfaadmin registry nuke --certs $ sfaadmin registry import_registry |
|||
#1031 | wontfix | "No such site" error reported when new project is added to Stitching Compute Service (SCS) | ||
Description |
The ION aggregate seems to die if the project name (sub-authority) contains a hyphen. It also dies if there is a hyphen in the client_ids. Sample errors: ERROR:omni: {'output': "Internal API error: <Fault 102: 'person_id 2: AddPersonToSite: Invalid argument: No such site'>", 'geni_api': 2, 'code': {'am_type': 'sfa', 'geni_code': 5, 'am_code': 5}, 'value': ''} ERROR:omni: {'output': "Internal API error: <Fault 102: 'person_id 2: AddSite: Invalid argument: Login base must consist only of lowercase ASCII letters or numbers'>", 'geni_api': 2, 'code': {'am_type': 'sfa', 'geni_code': 5, 'am_code': 5}, 'value': ''} |
Note: See TracQuery
for help on using queries.