#9 closed task (fixed)
Get iticket from iRODS for the experiment
| Reported by: | johren@bbn.com | Owned by: | koneil@bbn.com |
|---|---|---|---|
| Priority: | major | Milestone: | GEC17 |
| Component: | InitScript | Version: | Sprint1 |
| Keywords: | Cc: | ||
| Dependencies: |
Description
An iticket will be obtained from iRODS for a given experiment to provide access to the experiment directory for the executing iRODS user (i.e. the experimenter running the init script). This ticket should provide access for the omlserver iRODS user.
Change History (6)
comment:1 Changed 10 years ago by
| Component: | Authentication/Authorization → InitScript |
|---|---|
| Version: | SPIRAL5 → Sprint1 |
comment:2 Changed 10 years ago by
| Status: | new → assigned |
|---|
comment:3 Changed 10 years ago by
We have a related issue over at MyTestbed? for integration with OML [0].
comment:4 Changed 10 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:5 Changed 10 years ago by
Hi,
I'm working on interfacing this as a follow-up action to the OML server closing a database.
What is the URL scheme to obtain this ticket, and what form does the ticket take?
comment:6 Changed 10 years ago by
| Milestone: | → GEC17 |
|---|
Note: See
TracTickets for help on using
tickets.
I have a script that creates and returns the ticket for the experiment directory. It can take in a set of users to restrict access to (like the omlserver iRODS user) and an expiration time for the ticket.