Constructors¶

Net::OAuth2::AccessToken->new(%options)

 -Option           --Default
  access_token       undef
  auto_refresh       <false>
  changed            <false>
  error              undef
  error_description  <value of error>
  error_uri          undef
  expires_at         undef
  expires_in         undef
  profile            <required>
  refresh_always     BOOLEAN
  refresh_token      false
  scope              undef
  token_type         undef
    

Net::OAuth2::AccessToken->session_thaw($session, %options)

Pass in the output of a session_freeze() call in the past (maybe even for an older version of this module) and get the token object revived. This $session is a HASH.

You may pass any of the parameters for new() as %options, to overrule the values inside the $session.

 -Option --Default
  profile  <required>
    

  my $auth    = Net::OAuth2::Profile::WebServer->new(...);
  my $token   = $auth->get_access_token(...);
  my $session = $token->session_freeze;
  # now save $session in database or file
  ...
  # restore session
  my $auth    = Net::OAuth2::Profile::WebServer->new(...);
  my $token   = Net::OAuth2::AccessToken->session_thaw($session
    , profile => $auth);

Accessors¶

$obj->access_token()

Returns the (base64 encoded version of the) access token. The token will get updated first, if it has expired and refresh_token is enabled, or when new(auto_refresh) is set.

It does not matter that the token is base64 encoded or not: it will always need to be base64 encoded during transport.

$obj->attribute(NAME)

[0.58] Sometimes, the token gets attributes which are not standard; they have no official accessor (yet?). You can get them with this generic accessor.

$obj->changed( [BOOLEAN] )

[0.52] The session (token) needs to be saved, because any of the crucial parameters have been modified and "auto_save" is not defined by the profile.

$obj->hd()

$obj->profile()

$obj->scope()

$obj->state()

$obj->token_type()

errors

When the token is received (hence this object created) it be the result of an error. It is the way the original code was designed...

$obj->error()

$obj->error_description()

$obj->error_uri()

Expiration

$obj->auto_refresh()

$obj->expired( [$after] )

Returns true when the token has an expiration set and that time has passed. We use this token $after this check: to avoid the token to timeout inbetween, we take (by default 15 seconds) margin.

$obj->expires_at( [$timestamp] )

Returns the expiration timestamp of this token (true) or "undef" (false) when it is not set.

$obj->expires_in()

Returns the number of seconds left, before the token is expired. That may be negative.

$obj->refresh_always()

$obj->refresh_token()

$obj->update_token( $token, $tokentype, $expires_at, [$refresh_token] )

Change the token.

Actions¶

$obj->refresh()

Refresh the token, even if it has not expired yet. Returned is the new access_token value, which may be undef on failure.

$obj->session_freeze(%options)

This returns a SESSION (a flat HASH) containing all token parameters which needs to be saved to be able to restore this token later. This SESSION can be passed to session_thaw() to get revived.

The "changed" flag will be cleared by this method.

Be sure that your storage is character-set aware. For instance, you probably want to set 'mysql_enable_utf8' when you store this in a MySQL database. Perl's JSON module will output utf8 by default.

$obj->to_json()

Freeze this object into JSON. The JSON syntax is also used by the OAuth2 protocol, so a logical choice to provide. However, generically, the session_freeze() method provided.

HTTP

The token can be encoded in transport protocol in different ways. Using these method will add the token to the HTTP messages sent.

$obj->delete( $uri, [$header, [$content]] )

$obj->get( $uri, [$header, [$content]] )

$obj->post( $uri, [$header, [$content]] )

$obj->put( $uri, [$header, [$content]] )

$obj->request($request)