I-Series OAuth2.0 101 server connection errors

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Rewind!
    Somehow it works....

    Site Contributor
    VIP Subscriber
    50+ Posts
    • Jan 2019
    • 89

    #1

    I-Series OAuth2.0 101 server connection errors

    Morning all!

    We are getting a 101 error setting up the OAuth2.0 on a C360i (FW GC2-RF). Confirming the google account being used has 2FA enbled. I understand we can use a generated "App Password" but we were testing to see how this function works on the google workspace side. We configured the needed webdav settings based on the OAuth2.0 service doc, confirmed time, and other relevant settings related to the scan to email function and keep receiving this error. Wanted to touch base to see if anyone else has had a similar issue, and the steps taken to correct the issue.

    Thanks!

    JC
  • Synthohol
    Certified Konica Expert

    Site Contributor
    5,000+ Posts
    • Mar 2016
    • 5790

    #2
    IIRC, about half a decade ago google stopped the ability to use google hosted domains email and most of us just create a personal gmail just for the copier to use to circumvent this entirely.
    google workspace or whatever they call it removed the ability to create or use app passwords but the personal accounts still allow it.
    We know a thing or two because we've seen a thing or two.
    The medication helps though...

    Comment

    • tsbservice
      Field tech

      Site Contributor
      5,000+ Posts
      • May 2007
      • 7961

      #3
      @JC
      This is very new so we didn't test it till now.
      Thanks for heads up need some time to setup in house.
      A tree is known by its fruit, a man by his deeds. A good deed is never lost, he who sows courtesy, reaps friendship, and he who plants kindness gathers love.
      Blessed are they who can laugh at themselves, for they shall never cease to be amused.

      Comment

      • and
        Technician

        50+ Posts
        • Oct 2011
        • 96

        #4
        1. Details of Symptom:
        Email sending fails when "Google" is set as the OAuth 2.0 provider and the email body is blank.

        2. Example of Reproduction
        ~Reproduction Environment~
        Model/FW : C361i/GC2-RF

        ~Reproduction Rate~
        100%

        ~Preparation~
        1. Turn on OAuth 2.0 authentication, then select the OAuth 2.0 provider to Google and touch OK.
        2. Perform Google authentication and make it successful.

        ~Procedure~
        1. Send an email with a blank email body.
        ~Result~
        Email sending fails with error code 101.

        Comment

        • copytechtrouble
          Technician

          50+ Posts
          • Nov 2020
          • 94

          #5
          there is a bulletin about this.
          basically the email body has to have something in it or it will fail with a 101 error. a quick work around is to add a space into the email body.
          Attached Files

          Comment

          • Rewind!
            Somehow it works....

            Site Contributor
            VIP Subscriber
            50+ Posts
            • Jan 2019
            • 89

            #6
            Morning all! Thank you for the info. Confirming this resolved the issue. Here I was overthinking the issue thinking it was network related and was going to trace my packets to the google server smh. Thank you all again!

            Comment

            • NN-GG
              Tech-IT
              • Mar 2024
              • 11

              #7
              Originally posted by Synthohol
              IIRC, about half a decade ago google stopped the ability to use google hosted domains email and most of us just create a personal gmail just for the copier to use to circumvent this entirely.
              google workspace or whatever they call it removed the ability to create or use app passwords but the personal accounts still allow it.


              FYI:
              Here are the important links for it. Google Workspace account APP password is still supported, but 2FA must be turned on in the Admin console:

              Starting January 2025, less secure apps, third-party apps, or devices that have you sign in with only your username and password will no longer be supported for Google Workspace accounts. For exact



              We will continue to support App Specific Passwords (ASPs) for POP/IMAP/SMTP With LSA deprecation, will be blocking the ability to authenticate with a user's actual Google Credentials. However, users can still creature unique credentials via ASP. Customers have two options: 1) Use an app that suppo...



              Not so much for MS account, for Outlook account(already deprecated), and Microsoft 365 account ( plan to be deprecated in September 2025).

              Hope this helps anyone in the future who is reading this! 😉

              Comment

              Working...