Authorizing @{class:PhabricatorOAuthServerClient}s and generating @{class:PhabricatorOAuthServerAuthorizationCode}s
Authorizing @{class:PhabricatorOAuthServerClient}s and generating @{class:PhabricatorOAuthServerAuthorizationCode}s
- public function userHasAuthorizedClient($scope)
- public function authorizeClient($scope)
- public function generateAuthorizationCode($redirect_uri)
Validating @{class:PhabricatorOAuthServerAuthorizationCode}s and generating @{class:PhabricatorOAuthServerAccessToken}s
Validating @{class:PhabricatorOAuthServerAuthorizationCode}s and generating @{class:PhabricatorOAuthServerAccessToken}s
- public function generateAccessToken()
- public function validateAuthorizationCode($test_code, $valid_code)
- public function authorizeToken($token)
Internals
Internals
No methods for this task.
Other Methods
Other Methods
- public function __get($name)
- public function __set($name, $value)
- public function current()
- public function key()
- public function next()
- public function rewind()
- public function valid()
- private function throwOnAttemptedIteration()
- public function getPhobjectClassConstant($key, $byte_limit) — Read the value of a class constant.
- private function getUser()
- public function setUser($user)
- private function getClient()
- public function setClient($client)
- public function validateRedirectURI($uri)
- public function assertValidRedirectURI($raw_uri) — See http://tools.ietf.org/html/draft-ietf-oauth-v2-23#section-3.1.2 for details on what makes a given redirect URI "valid".
- public function validateSecondaryRedirectURI($secondary_uri, $primary_uri) — If there's a URI specified in an OAuth request, it must be validated in its own right. Further, it must have the same domain, the same path, the same port, and (at least) the same query parameters as the primary URI.