IdToken::getClaims() - Code Metrics - php-guard/oauth-server - Measure and Improve Code Quality continuously with Scrutinizer

IdToken::getClaims() A
last analyzed 2018-06-23 21:42 UTC

↳ Parent: IdToken

Complexity

Conditions	1
Paths	1

Size

Total Lines

Duplication

Lines	0
Ratio	0 %

Importance

Changes

Metric	Value
cc	1
nc	1
nop	0
dl	0
loc	3
rs	10
c	0
b	0
f	0

<?php
/**
 * Created by PhpStorm.
 * User: Alexandre
 * Date: 18/02/2018
 * Time: 17:51
 */

namespace OAuth2;


use Firebase\JWT\JWT;
filter:
    dependency_paths: ["lib/*"]

class IdToken implements IdTokenInterface
{
    /**
     * @var array
     */
    protected $claims;

    /**
     * IdToken constructor.
     * @param array $claims
     * @throws \Exception
     */
    public function __construct(array $claims)
    {
//        $missingClaims = array_diff(self::REQUIRED_CLAIMS, array_keys($claims));

//        if (!empty($missingClaims)) {
//            throw new \Exception('Missing claims : ' . implode(', ', $missingClaims));
//        }

//        $undefinedClaims = array_diff(array_keys($claims), self::DEFINED_CLAIMS);

//        if (!empty($undefinedClaims)) {
//            throw new \Exception('Undefined claims : ' . implode(', ', $undefinedClaims));
//        }

        // todo check nonce required if present in authentication request
        // todo check auth_time if max_age request is made or auth_time is required via config

        $this->claims = $claims;
    }

public function getClaims() : array
    {
       return $this->claims;
    }

    /**
     * Specify data which should be serialized to JSON
     * @link http://php.net/manual/en/jsonserializable.jsonserialize.php
     * @return mixed data which can be serialized by <b>json_encode</b>,
     * which is a value of any type other than a resource.
     * @since 5.4.0
     */
    public function jsonSerialize()
    {
        return JWT::encode($this->getClaims(), 'key');
    }
}

1			<?php
2			/**
3			* Created by PhpStorm.
4			* User: Alexandre
5			* Date: 18/02/2018
6			* Time: 17:51
7			*/
8
9			namespace OAuth2;
10
11
12			use Firebase\JWT\JWT;
			0 ignored issues – show Bug introduced 2018-05-20 17:05 UTC by Report Bug Copy Issue Report The type `Firebase\JWT\JWT` was not found. Maybe you did not declare it correctly or list all dependencies? The issue could also be caused by a filter entry in the build configuration. If the path has been excluded in your configuration, e.g. `excluded_paths: ["lib/"]`, you can move it to the dependency path list as follows: filter: dependency_paths: ["lib/"] For further information see https://scrutinizer-ci.com/docs/tools/php/php-scrutinizer/#list-dependency-paths Loading history...
13
14			class IdToken implements IdTokenInterface
15			{
16			/**
17			* @var array
18			*/
19			protected $claims;
20
21			/**
22			* IdToken constructor.
23			* @param array $claims
24			* @throws \Exception
25			*/
26			public function __construct(array $claims)
27			{
28			// $missingClaims = array_diff(self::REQUIRED_CLAIMS, array_keys($claims));
			0 ignored issues – show Unused Code Comprehensibility introduced 2018-04-21 16:24 UTC by Report Bug Copy Issue Report `57%` of this comment could be valid code. Did you maybe forget this after debugging? Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
29			// if (!empty($missingClaims)) {
30			// throw new \Exception('Missing claims : ' . implode(', ', $missingClaims));
31			// }
32
33			// $undefinedClaims = array_diff(array_keys($claims), self::DEFINED_CLAIMS);
			0 ignored issues – show Unused Code Comprehensibility introduced 2018-04-21 16:24 UTC by Report Bug Copy Issue Report `57%` of this comment could be valid code. Did you maybe forget this after debugging? Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
34			// if (!empty($undefinedClaims)) {
35			// throw new \Exception('Undefined claims : ' . implode(', ', $undefinedClaims));
36			// }
37
38			// todo check nonce required if present in authentication request
39			// todo check auth_time if max_age request is made or auth_time is required via config
40
41			$this->claims = $claims;
42			}
43
44			public function getClaims() : array
45			{
46			return $this->claims;
47			}
48
49			/**
50			* Specify data which should be serialized to JSON
51			* @link http://php.net/manual/en/jsonserializable.jsonserialize.php
52			* @return mixed data which can be serialized by <b>json_encode</b>,
53			* which is a value of any type other than a resource.
54			* @since 5.4.0
55			*/
56			public function jsonSerialize()
57			{
58			return JWT::encode($this->getClaims(), 'key');
59			}
60			}

php-guard / oauth-server

IdToken::getClaims() A last analyzed 2018-06-23 21:42 UTC

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like

IdToken::getClaims() A
last analyzed 2018-06-23 21:42 UTC