title: Securly Storing OpenID identifiers and OAuth tokens
body: <p>I am creating a web app that will use OpenID logins and OAuth tokens with Youtube.  I am currently storing the OpenID identity and OAuth token/token secret in plain text in the database.</p>
  
  <p>Is it inappropriate to store these values as plain text?  I could use a one-way encryption for the OpenID identifier but I don't know if that is necessary.  For the OAuth tokens, I would need to use a two-way encryption as my app relies on getting the session token for some uses.</p>
  
  <p>Is it necessary to encrypt the OpenID identity?  Could someone use it to gain access to a user's account?</p>