# REST API authentication strategies when using OpenID

**URL:** <https://www.ruby-forum.com/t/rest-api-authentication-strategies-when-using-openid/153243>\
**Category:** Rails\
**Created:** [November 13, 2008, 8:51pm UTC](https://www.ruby-forum.com/t/rest-api-authentication-strategies-when-using-openid/153243 "2008-11-13T20:51:12Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![kuma](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/a587f6/32.png) [@kuma](https://www.ruby-forum.com/u/kuma)\
**Post date:** [November 13, 2008, 8:51pm UTC](https://www.ruby-forum.com/t/rest-api-authentication-strategies-when-using-openid/153243/1 "2008-11-13T20:51:12Z")

</div>

What sort of mechanisms are people using to expose their APIs to people  
if  
they use OpenID?

On a recent project, I just generated an email + api key pair for each  
account and I tell people to use that, then my authentication system  
looks  
for that in lieu of openID credentials. I’d really be interested to see  
what others are doing.

Thanks!

-Brian