Random characters appended in URL

I am trying to use the Open and Fill option from Windows app and the URL that opens has some random characters appended to it. Now for good websites it does not cause any problems but for some websites the page won't load. Can this be disabled?


1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided

Comments

  • ag_ana
    ag_ana
    1Password Alumni

    Hi @iamharshkumar97!

    Do you see these characters inside the website field of these items in 1Password?

  • iamharshkumar97
    iamharshkumar97
    Community Member

    @ag_ana No. In the website field I have just the website URL. And I have noticed that it changes at each instance of open and fill for the same website.

  • ag_ana
    ag_ana
    1Password Alumni

    @iamharshkumar97:

    And I have noticed that it changes at each instance of open and fill for the same website.

    Thank you for the confirmation! In this case, it's the website itself that is doing that, and 1Password has no control over it. You probably would see the same behavior even if you get to the login page directly by clicking through the Adobe website, without using 1Password at all. Can you confirm this is the case?

  • iamharshkumar97
    iamharshkumar97
    Community Member

    @ag_ana No that is not the case. When I visit Adobe's login page it is a

    https://auth.services.adobe.com/en_US/deeplink.html?deeplink=ssofirst&callback=https%3A%2F%2Fims-na1.adobelogin.com%2Fims%2Fadobeid%2FSunbreakWebUI1%2FAdobeID%2Ftoken%3Fredirect_uri%3Dhttps%253A%252F%252Faccount.adobe.com%252F%2523from_ims%253Dtrue%2526old_hash%253D%2526api%253Dauthorize%2526reauth%253Dtrue%26code_challenge_method%3Dplain%26use_ms_for_expiry%3Dtrue&client_id=SunbreakWebUI1&scope=AdobeID%2Copenid%2Cacct_mgmt_api%2Cgnav%2Csao.cce_private%2Csao.digital_editions%2Ccreative_cloud%2Cread_countries_regions%2Csocial.link%2Cunlink_social_account%2Cadditional_info.address.mail_to%2Cclient.scopes.read%2Cpublisher.read%2Cadditional_info.account_type%2Cadditional_info.roles%2Cadditional_info.social%2Cadditional_info.screen_name%2Cadditional_info.optionalAgreements%2Cadditional_info.secondary_email%2Cadditional_info.secondary_email_verified%2Cadditional_info.phonetic_name%2Cadditional_info.dob%2Cupdate_profile.all%2Csecurity_profile.read%2Csecurity_profile.update%2Cadmin_manage_user_consent%2Cadmin_slo%2Cpiip_write%2Cmps%2Clast_password_update%2Cupdate_email%2Caccount_cluster.read%2Caccount_cluster.update%2Cadditional_info.authenticatingAccount%2Creauthenticated&denied_callback=https%3A%2F%2Fims-na1.adobelogin.com%2Fims%2Fdenied%2FSunbreakWebUI1%3Fredirect_uri%3Dhttps%253A%252F%252Faccount.adobe.com%252F%2523from_ims%253Dtrue%2526old_hash%253D%2526api%253Dauthorize%2526reauth%253Dtrue%26response_type%3Dtoken&relay=348ef1f4-4f71-446a-b85a-d8a8ba2967d6&locale=en_US&flow_type=token&ctx_id=accmgmt&idp_flow_type=login&reauthenticate=force#/

    This is fine. The pattern that I am seeing is that /?... followed by random characters is being appended only when I open it through 1Password's Windows app. This was the case with all the websites that I tried including my banks which does not append any tracking url at the end and has a clean url for login.

  • Blake
    edited June 2021

    Hi @iamharshkumar97

    The random strings that are appended to the end of URLs, when launching websites from the 1Password desktop app, are item references that enable Go&Fill with the new browser integration feature.

    These random strings are like a secret handshake between the desktop app and 1Password in your browser, telling 1Password in your browser what item to fill when the page loads. Those strings do not contain any secrets or password/username data. This cannot be disabled.

  • Bufto
    Bufto
    Community Member

    Further, these random strings cause failure of user/password fields being recognized filled in by 1password, so the whole login process becomes a nightmare. If delete these characters and reload the page, the login fields are then discovered and recognized. There has to be a solution to this or the program is very much unusable

This discussion has been closed.