Opened 12 years ago
Closed 12 years ago
#75 closed (fixed)
Slice's URN should have an authority matching it's SA
Reported by: | sedwards@bbn.com | Owned by: | somebody |
---|---|---|---|
Priority: | major | Milestone: | 2012-09-04 client release |
Component: | Clients | Version: | |
Keywords: | v0.6.0 | Cc: | |
Dependencies: |
Description
I managed to create a Slice object with a URN that doesn't match the authority of it's SA.
<sa name="urn:publicid:IDN+mySA+authority+sa" organization="urn:publicid:IDN+gmoc.geni.net+organization+myWork" pop="urn: publicid:IDN+gmoc.geni.net+pop+myPop" type="protogeni" urn="urn:publicid:IDN+mySA+authority+sa" version="1.0"> <slice created="1346717238" expires="1346702838" operator="urn:publicid:IDN+gmoc.geni.net+organization+myWork" primary_contact="jdoe@example.com" urn="urn:publicid:IDN+gmoc.geni.net+slice+mySlice" uuid="12345678-1234-1234-1234-123456789012"/> </sa>
Perhaps we should require the full URN filled in for the Slice
object's identifier instead of constructing it?
Change History (4)
comment:1 Changed 12 years ago by
comment:2 Changed 12 years ago by
Keywords: | v0.6.0 added; v0.5.3 removed |
---|
I think this is still true in 0.6.0.
comment:3 Changed 12 years ago by
Kevin will validate that it's a URN and if not throw an exception.
comment:4 Changed 12 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
This is fixed in 0.6.1. Closing.
Note: See
TracTickets for help on using
tickets.
In my opinion, verifying that the URN matches the SA's authority is too much trouble for now, but we should require a full URN rather than constructing one in the Slice case.