Issue: OAuth2 redirect URI comparison should support exact string matching

Issue: OAuth2 redirect URI comparison should support exact string matching: a task in LegoFlow-SWE (Harbor dataset). Currently, client redirect URIs are stored internally as parsed url::Url objects. During OAuth2 authorization, the incoming redirect uri is also parsed and the two are compared…

The task

Currently, client redirect URIs are stored internally as parsed `url::Url` objects. During OAuth2 authorization, the incoming `redirect_uri` is also parsed and the two are compared semantically (e.g., normalization of trailing slashes, query parameter ordering). According to RFC 6749, redirect URI comparison must be…

Part of Lego-X/LegoFlow-SWE.