auth: mech-oauth2 - Rename continued data to reponse data/payload

Makes more sense in SASL overall

diff --git a/src/auth/mech-oauth2.c b/src/auth/mech-oauth2.c
index f35508331cd97c58bc0e2e186fc93c6b60f2ef42..56182f4ebdca0cd792dca6dd4828b029cd5629df 100644 (file)
--- a/src/auth/mech-oauth2.c
+++ b/src/auth/mech-oauth2.c
@@ -262,7 +262,7 @@ mech_oauthbearer_auth_continue(struct auth_request *request,
        const char *token = NULL;
        /* ensure initial field is OK */
        if (*fields == NULL || *(fields[0]) == '\0') {
-               e_info(request->mech_event, "Invalid continued data");
+               e_info(request->mech_event, "Invalid response payload");
                oauth2_fail_invalid_request(oauth2_req);
                return;
        }
@@ -311,7 +311,7 @@ mech_oauthbearer_auth_continue(struct auth_request *request,
                                token = value;
                        } else {
                                e_info(request->mech_event,
-                                      "Invalid continued data");
+                                      "Invalid response payload");
                                oauth2_fail_invalid_token(oauth2_req);
                                return;
                        }
@@ -378,7 +378,7 @@ mech_xoauth2_auth_continue(struct auth_request *request,
                                token = value;
                        } else {
                                e_info(request->mech_event,
-                                      "Invalid continued data");
+                                      "Invalid response data");
                                oauth2_fail_invalid_token(oauth2_req);
                                return;
                        }