Ad a)
Yes, 2 different usecases, that is why I mentioned the 'link in the email' usecase should just make it possible to finish one specific task. The other one is a real SSO usecase. The latter should be solved by a standard, the former should be solved by a 'very simple token' (indeed no SAML here) Creating a simple SHA-256 hash over some known data and e.g. a salt and assigning the task to this 'token' solves this issue. In that case you cannot use it to do anything else, just finish this task. This latter usecase can be easily done in your own code, no need for anything else and no need to add it to Activiti
Ad b) OpenAM is a full solution, which was 'a proposal', just using OpenSAML would require a lot less. Administration in our case (and external ones) never fitted in the Activiti user/group model anyway (remarkably (not!) enough the OpenAM one did since it is really targeted at I&AM), and often there are existing solutions. So we 'just' use the activity engine and no user/group management.
As Daniel stated, I do not see a kind of SSO solution being embedded in the core, including the token for email…