Interface Nexus\Mcp\Client\Auth\UserAuthorizationInterface

The one leg of the OAuth flow the SDK cannot perform: putting the authorization URL in front of a resource owner and collecting the redirect the user-agent lands on. The SDK owns PKCE, the state value, the expected issuer, the URL it builds, and every validation of the response. An implementation only has to open $redirect->url and return where the user-agent ended up.

Located at Client/Auth/UserAuthorizationInterface.php

Methods
`public`	`authorize(AuthorizationRedirect $redirect, Cancellation $cancellation): AuthorizationCallback` Reports the redirect URI the user-agent arrived at once the resource owner has answered. The implementation yields to the event loop while it waits rather than blocking it, and gives up when `$cancellation` fires, which happens when the request that needs the token is abandoned. Reports the redirect URI the user-agent arrived at once the resource owner has answered. The implementation yields to the event loop while it waits rather than blocking it, and gives up when `$cancellation` fires, which happens when the request that needs the token is abandoned.	#

Namespaces

Classes

Interfaces

Enums

Interface Nexus\Mcp\Client\Auth\UserAuthorizationInterface