Use this HTML page to show the authorization code of an OAuth client that did not specify a client redirection URI upon partner registration.
When the OAuth client does not specify a client redirection URI or cannot receive redirects, the authorization server does not know where to send the resource owner after authorization. The OAuth client does not receive the authorization code required to exchange for an access token or refresh token.
The Tivoli® Federated Identity Manager provides an HTML template page called user_response.html. This page shows the authorization code that the resource owner can provide to a trusted OAuth client.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>OAuth - Response</title>
</head>
<body>
<h1>OAuth - Response</h1>
<br />
<p>Your OAuth client did not provide a redirect URI.
Supply this value to your client:</p>
<br />
<p>OAuth Authorization Code: <span class="client">@OAUTH_CODE@</span></p>
</body>
</html>