o ÿÑÐbnã@sTddlmZddlmZddlmZddlmZGdd„deƒZ dd „Z d d „Z d S) é)Údefault_json_headers©Úgenerate_token)Úadd_params_to_urié)ÚInvalidRequestErrorc@s`eZdZdZdZdZdZdZdd„Zdd „Z d d „Z d d „Z dd„Z dd„Z dd„Zdd„ZdS)ÚDeviceAuthorizationEndpointaY This OAuth 2.0 [RFC6749] protocol extension enables OAuth clients to request user authorization from applications on devices that have limited input capabilities or lack a suitable browser. Such devices include smart TVs, media consoles, picture frames, and printers, which lack an easy input method or a suitable browser required for traditional OAuth interactions. Here is the authorization flow:: +----------+ +----------------+ | |>---(A)-- Client Identifier --->| | | | | | | |<---(B)-- Device Code, ---<| | | | User Code, | | | Device | & Verification URI | | | Client | | | | | [polling] | | | |>---(E)-- Device Code --->| | | | & Client Identifier | | | | | Authorization | | |<---(F)-- Access Token ---<| Server | +----------+ (& Optional Refresh Token) | | v | | : | | (C) User Code & Verification URI | | : | | v | | +----------+ | | | End User | | | | at |<---(D)-- End user reviews --->| | | Browser | authorization request | | +----------+ +----------------+ This DeviceAuthorizationEndpoint is the implementation of step (A) and (B). (A) The client requests access from the authorization server and includes its client identifier in the request. (B) The authorization server issues a device code and an end-user code and provides the end-user verification URI. Zdevice_authorizationÚstringiécCs ||_dS©N)Úserver)Úselfr ©rú^/var/www/secure340b-portal/env/lib/python3.10/site-packages/authlib/oauth2/rfc8628/endpoint.pyÚ__init__<s z$DeviceAuthorizationEndpoint.__init__cCs | |¡Sr )Úcreate_endpoint_response©r ÚrequestrrrÚ__call__?s z$DeviceAuthorizationEndpoint.__call__cCs |j |¡Sr )r Zcreate_oauth2_requestrrrrÚcreate_endpoint_requestDs z3DeviceAuthorizationEndpoint.create_endpoint_requestcCsv|jstdƒ‚|j |j¡| ¡}| ¡}| ¡}t|d|fgƒ}|||||j |j dœ}|  |j|j|¡d|t fS)NzMissing "client_id" in payloadÚ user_code)Ú device_coderÚverification_uriÚverification_uri_completeZ expires_inÚintervaléÈ) Ú client_idrr Zvalidate_requested_scopeÚscopeÚgenerate_device_codeÚgenerate_user_codeÚget_verification_urirÚ EXPIRES_INÚINTERVALÚsave_device_credentialr)r rrrrrÚdatarrrrGs$ ÿú z4DeviceAuthorizationEndpoint.create_endpoint_responsecCs|jdkrtƒStƒS)zåA method to generate ``user_code`` value for device authorization endpoint. This method will generate a random string like MQNA-JPOZ. Developers can rewrite this method to create their own ``user_code``. Zdigital)ÚUSER_CODE_TYPEÚcreate_digital_user_codeÚcreate_string_user_code©r rrrr`s z.DeviceAuthorizationEndpoint.generate_user_codecCstdƒS)zêA method to generate ``device_code`` value for device authorization endpoint. This method will generate a random string of 42 characters. Developers can rewrite this method to create their own ``device_code``. é*rr(rrrrjsz0DeviceAuthorizationEndpoint.generate_device_codecCótƒ‚)zìDefine the ``verification_uri`` of device authorization endpoint. Developers MUST implement this method in subclass:: def get_verification_uri(self): return 'https://your-company.com/active' ©ÚNotImplementedErrorr(rrrr qsz0DeviceAuthorizationEndpoint.get_verification_uricCr*)avSave device token into database for later use. Developers MUST implement this method in subclass:: def save_device_credential(self, client_id, scope, data): item = DeviceCredential( client_id=client_id, scope=scope, **data ) item.save() r+)r rrr$rrrr#zs z2DeviceAuthorizationEndpoint.save_device_credentialN)Ú__name__Ú __module__Ú __qualname__Ú__doc__Z ENDPOINT_NAMEr%r!r"rrrrrrr r#rrrrrs(  rcCsd}d td|ƒtd|ƒg¡S)NZBCDFGHJKLMNPQRSTVWXZú-é©Újoinr©Úbaserrrr'‰sr'cCs&d}d td|ƒtd|ƒtd|ƒg¡S)NÚ 0123456789r1ér3r5rrrr&Žs ýr&N) Zauthlib.constsrZauthlib.common.securityrZauthlib.common.urlsrZrfc6749.errorsrÚobjectrr'r&rrrrÚs