It might be better to fake a userId (u:camtest:foobar) than to use a wrong userId string as that will stop at the validation point.

There is also a bit of code in oae-authentication/api.js in the associateLoginId method that can be removed
```
                if (!user) {
                    return callback({'code': 404, 'msg': 'User does not exist.'});
                }
```

The PrincipalAPI will return a 404 error if the user could not be found, so there is no need for a !user check