REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-09 00:14:06 +02:00
< ? php
/**
* Authorize Application Screen
*
* @ package WordPress
* @ subpackage Administration
*/
/** WordPress Administration Bootstrap */
require_once __DIR__ . '/admin.php' ;
$error = null ;
$new_password = '' ;
if ( isset ( $_POST [ 'action' ] ) && 'authorize_application_password' === $_POST [ 'action' ] ) {
check_admin_referer ( 'authorize_application_password' );
$success_url = $_POST [ 'success_url' ];
$reject_url = $_POST [ 'reject_url' ];
$app_name = $_POST [ 'app_name' ];
2020-10-22 17:06:09 +02:00
$app_id = $_POST [ 'app_id' ];
REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-09 00:14:06 +02:00
$redirect = '' ;
if ( isset ( $_POST [ 'reject' ] ) ) {
if ( $reject_url ) {
2020-10-22 04:44:05 +02:00
$redirect = $reject_url ;
REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-09 00:14:06 +02:00
} else {
$redirect = admin_url ();
}
} elseif ( isset ( $_POST [ 'approve' ] ) ) {
2020-10-22 17:06:09 +02:00
$created = WP_Application_Passwords :: create_new_application_password (
get_current_user_id (),
array (
'name' => $app_name ,
'app_id' => $app_id ,
)
);
REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-09 00:14:06 +02:00
if ( is_wp_error ( $created ) ) {
$error = $created ;
} else {
list ( $new_password ) = $created ;
if ( $success_url ) {
$redirect = add_query_arg (
array (
'username' => urlencode ( wp_get_current_user () -> user_login ),
'password' => urlencode ( $new_password ),
),
$success_url
);
}
}
}
if ( $redirect ) {
// Explicitly not using wp_safe_redirect b/c sends to arbitrary domain.
wp_redirect ( $redirect );
exit ;
}
}
$title = __ ( 'Authorize Application' );
$app_name = ! empty ( $_REQUEST [ 'app_name' ] ) ? $_REQUEST [ 'app_name' ] : '' ;
2020-10-22 17:06:09 +02:00
$app_id = ! empty ( $_REQUEST [ 'app_id' ] ) ? $_REQUEST [ 'app_id' ] : '' ;
REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-09 00:14:06 +02:00
$success_url = ! empty ( $_REQUEST [ 'success_url' ] ) ? $_REQUEST [ 'success_url' ] : null ;
2020-10-22 04:44:05 +02:00
if ( ! empty ( $_REQUEST [ 'reject_url' ] ) ) {
$reject_url = $_REQUEST [ 'reject_url' ];
} elseif ( $success_url ) {
$reject_url = add_query_arg ( 'success' , 'false' , $success_url );
} else {
$reject_url = null ;
}
$user = wp_get_current_user ();
REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-09 00:14:06 +02:00
2020-10-22 17:06:09 +02:00
$request = compact ( 'app_name' , 'app_id' , 'success_url' , 'reject_url' );
REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-09 00:14:06 +02:00
$is_valid = wp_is_authorize_application_password_request_valid ( $request , $user );
if ( is_wp_error ( $is_valid ) ) {
wp_die (
__ ( 'The Authorize Application request is not allowed.' ) . ' ' . implode ( ' ' , $is_valid -> get_error_messages () ),
__ ( 'Cannot Authorize Application' )
);
}
if ( ! wp_is_application_passwords_available_for_user ( $user ) ) {
if ( wp_is_application_passwords_available () ) {
$message = __ ( 'Application passwords are not enabled for your account. Please contact the site administrator for assistance.' );
} else {
$message = __ ( 'Application passwords are not enabled.' );
}
wp_die (
$message ,
__ ( 'Cannot Authorize Application' ),
array (
'link_text' => __ ( 'Go Back' ),
'link_url' => $reject_url ? add_query_arg ( 'error' , 'disabled' , $reject_url ) : admin_url (),
)
);
}
wp_enqueue_script ( 'auth-app' );
wp_localize_script (
'auth-app' ,
'authApp' ,
array (
'user_login' => $user -> user_login ,
'success' => $success_url ,
'reject' => $reject_url ? $reject_url : admin_url (),
)
);
require_once ABSPATH . 'wp-admin/admin-header.php' ;
?>
< div class = " wrap " >
< h1 >< ? php echo esc_html ( $title ); ?> </h1>
< ? php if ( is_wp_error ( $error ) ) : ?>
< div class = " notice notice-error " >< p >< ? php echo $error -> get_error_message (); ?> </p></div>
< ? php endif ; ?>
< div class = " card js-auth-app-card " >
< h2 class = " title " >< ? php __ ( 'An application would like to connect to your account.' ); ?> </h2>
< ? php if ( $app_name ) : ?>
< p >
< ? php
2020-10-09 03:06:03 +02:00
/* translators: %s: Application name. */
REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-09 00:14:06 +02:00
printf ( __ ( 'Would you like to give the application identifying itself as %s access to your account? You should only do this if you trust the app in question.' ), '<strong>' . esc_html ( $app_name ) . '</strong>' );
?>
</ p >
< ? php else : ?>
< p >< ? php _e ( 'Would you like to give this application access to your account? You should only do this if you trust the app in question.' ); ?> </p>
< ? php endif ; ?>
2020-10-22 04:36:11 +02:00
< ? php
if ( is_multisite () ) {
$blogs = get_blogs_of_user ( $user -> ID , true );
if ( count ( $blogs ) > 1 ) {
?>
< p >
< ? php
printf (
/* translators: 1: url to my-sites.php, 2: Number of blogs the user has. */
_n (
'This will grant access to <a href="%1$s">the %2$s blog in this installation that you have permissions on</a>.' ,
'This will grant access to <a href="%1$s">all %2$s blogs in this installation that you have permissions on</a>.' ,
count ( $blogs )
),
admin_url ( 'my-sites.php' ),
number_format_i18n ( count ( $blogs ) )
);
?>
</ p >
< ? php
}
}
?>
REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-09 00:14:06 +02:00
< ? php if ( $new_password ) : ?>
< div class = " notice notice-success notice-alt below-h2 " >
< p class = " password-display " >
< ? php
printf (
/* translators: 1: Application name, 2: Generated password. */
__ ( 'Your new password for %1$s is %2$s.' ),
'<strong>' . esc_html ( $app_name ) . '</strong>' ,
'<kbd>' . esc_html ( WP_Application_Passwords :: chunk_password ( $new_password ) ) . '</kbd>'
);
?>
</ p >
</ div >
< ? php
/**
* Fires in the Authorize Application Password new password section .
*
* @ since 5.6 . 0
*
* @ param string $new_password The newly generated application password .
* @ param array $request The array of request data . All arguments are optional and may be empty .
* @ param WP_User $user The user authorizing the application .
*/
do_action ( 'wp_authorize_application_password_form' , $request , $user );
?>
< ? php else : ?>
< form action = " <?php echo esc_url( admin_url( 'authorize-application.php' ) ); ?> " method = " post " >
< ? php wp_nonce_field ( 'authorize_application_password' ); ?>
< input type = " hidden " name = " action " value = " authorize_application_password " />
2020-10-22 17:06:09 +02:00
< input type = " hidden " name = " app_id " value = " <?php echo esc_attr( $app_id ); ?> " />
REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-09 00:14:06 +02:00
< input type = " hidden " name = " success_url " value = " <?php echo esc_url( $success_url ); ?> " />
< input type = " hidden " name = " reject_url " value = " <?php echo esc_url( $reject_url ); ?> " />
< label for = " app_name " >< ? php esc_html_e ( 'Application Title:' ); ?> </label>
< input type = " text " id = " app_name " name = " app_name " value = " <?php echo esc_attr( $app_name ); ?> " placeholder = " <?php esc_attr_e( 'Name this connection…' ); ?> " required />
< ? php
/**
* Fires in the Authorize Application Password form before the submit buttons .
*
* @ since 5.6 . 0
*
* @ param array $request {
* The array of request data . All arguments are optional and may be empty .
*
* @ type string $app_name The suggested name of the application .
* @ type string $success_url The url the user will be redirected to after approving the application .
* @ type string $reject_url The url the user will be redirected to after rejecting the application .
* }
* @ param WP_User $user The user authorizing the application .
*/
do_action ( 'wp_authorize_application_password_form' , $request , $user );
?>
< p >< ? php submit_button ( __ ( 'Yes, I approve of this connection.' ), 'primary' , 'approve' , false ); ?>
< br />< em >
< ? php
if ( $success_url ) {
printf (
2020-10-09 03:06:03 +02:00
/* translators: %s: The URL the user is being redirected to. */
REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-09 00:14:06 +02:00
__ ( 'You will be sent to %s' ),
'<strong><kbd>' . esc_html (
add_query_arg (
array (
'username' => $user -> user_login ,
'password' => '[------]' ,
),
$success_url
)
) . '</kbd></strong>'
);
} else {
_e ( 'You will be given a password to manually enter into the application in question.' );
}
?>
</ em >
</ p >
< p >< ? php submit_button ( __ ( 'No, I do not approve of this connection.' ), 'secondary' , 'reject' , false ); ?>
< br />< em >
< ? php
if ( $reject_url ) {
printf (
2020-10-09 03:06:03 +02:00
/* translators: %s: The URL the user is being redirected to. */
REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-09 00:14:06 +02:00
__ ( 'You will be sent to %s' ),
2020-10-22 04:44:05 +02:00
'<strong><kbd>' . esc_html ( $reject_url ) . '</kbd></strong>'
REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-09 00:14:06 +02:00
);
} else {
_e ( 'You will be returned to the WordPress Dashboard, and no changes will be made.' );
}
?>
</ em >
</ p >
</ form >
< ? php endif ; ?>
</ div >
</ div >
< ? php
require_once ABSPATH . 'wp-admin/admin-footer.php' ;