| 35 | | |
| 36 | | - Add a new external hook to allow the overwriting of the job's ticket |
| 37 | | (mainly username and billing code) at startup time : |
| 38 | | |
| 39 | | 1 - hook is launched and can do whatever it wants, like asking |
| 40 | | the user for username+password or billing code |
| 41 | | |
| 42 | | 2 - hook prints any (or all) of : |
| 43 | | |
| 44 | | USER:some_username |
| 45 | | BILLING:some_billingcode |
| 46 | | DENY |
| 47 | | |
| 48 | | if hook doesn't print anything, job processed as usual. |
| 49 | | if DENY, job is rejected. |
| 50 | | |
| 51 | | 3 - if billing code or username is invalid, and if PyKota |
| 52 | | is configured to loop in this case, hook is launched |
| 53 | | again, otherwise job is rejected. |
| 54 | | |
| 55 | | 4 - if billing code and/or username is valid, the job's |
| 56 | | billing code and/or username are overwritten with |
| 57 | | these values, and PyKota processes the job as usual. |
