| Commit message (Collapse) | Author | Age | Lines |
|---|
| |
|
|
| |
Forgot to commit the db migration.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Participants in /sys/mebmberships representation are now tagged with
their appropriate participant type:
main: mainparticipant
sub: subparticipant
anonym: anonymous participant
e.g.
[
{
"community": {
"name": "public",
"description": "For anonymous participants.",
"cid": 1
},
"participants": [
{
"pid": 2,
--> "type": "main",
"name": "Computation client",
"itsyou": true,
"description": "Computation client of NumLab service.",
"org": {
"abbr": "S",
"name": "Universität Stuttgart"
},
"mid": 1,
"email": "rudlof@rus.uni-stuttgart.de",
"dns": "nfldevvipecs.rus.uni-stuttgart.de"
},
...
This feature needs a database migration.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Up to now events could be turned on and off by resources. To turn on
events you still have to do it by resource but have additionally
the possibility to control it by participant. Only if both switches are
on, the participant will get events generated through the resource.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Now redirects are integrity secured by sha1 message digest.
A redirecting participant uses the /sys/auths resource realm
attribute to store a message digest over all relevant
redirect parameters (for details see [1]). The target
participant uses this message digest again and verifies the
integrity of the received redirect parameters
(Location-Header).
[1] see ECSA documentation at ECS->System resources->Auths
|
| | |
|
| |
|
|
|
| |
The ev_types table had been populated only if anonymous participants was
true.
|
| | |
|
| |
|
|
| |
Initialize code don't have access to model objects.
|
| | |
|
| | |
|
| |
|
|
|
| |
The authorization resource (/sys/auths) functionality is now provided
through the standard application resource infrastructure.
|
| |
|
