Problem/Motivation

As now, there is no validation for customer/primary account keys for Drupal 7 version.

Proposed resolution

Implement validation in translator settings form. While doing this we can update replace "Microsoft Customer ID" with "Client ID" and "Primary Account Key" with "Client secret" same as it is in D8.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mbovan created an issue. See original summary.

mbovan’s picture

Status: Active » Needs review
FileSize
4.11 KB

Added validation, tests and updated description of API keys fields.

Status: Needs review » Needs work

The last submitted patch, 2: validate_client_id_and-2653286-2.patch, failed testing.

mbovan’s picture

Test bot is complaining about missing tmgmt_translator_load()...

Status: Needs review » Needs work

The last submitted patch, 4: validate_client_id_and-2653286-4.patch, failed testing.

The last submitted patch, 4: validate_client_id_and-2653286-4.patch, failed testing.

miro_dietiker’s picture

Since we changed the naming of these keys already multiple times, i like to see a screenshot of the M$ UI with the proper naming of these keys.
(of course, wipe out the effektive key values.. ;-) )

The last submitted patch, 4: validate_client_id_and-2653286-4.patch, failed testing.

mbovan’s picture

Status: Needs work » Needs review
FileSize
17.25 KB

Here is the screenshot of Microsoft translator's user interface.

miro_dietiker’s picture

Thx for sending. I was more referring to the Microsoft side UI where the keys are created (sure with unreadable secrets ;-) ) to compare

mbovan’s picture

Issue summary: View changes
FileSize
60.27 KB

Here is the another one:

miro_dietiker’s picture

Looks consistent! Hope we didn't swap them. ;-)

Berdir’s picture

What exactly is the difference between this and #2655952: Add "Connect" button ?

mbovan’s picture

D7 and D8 version? In D7 we don't have parent::addConnectButton() or?

  • Berdir committed be62059 on 7.x-1.x authored by mbovan
    Issue #2653286 by mbovan: Validate client ID and secret keys
    
Berdir’s picture

Status: Needs review » Fixed

Uh, forget what I said :)

Wow, took me 15m+ to figure out again how to set this up. Super confusing. I thought we once improved the docs on what to do, did we only do that for 8.x?

We should also finally remove the old API key field.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.