TT-4275 Update dev portal object

[sredxny]

update the dev portal object so when it calls update method the information is not lost

Description

As TIB didn't know about new dev-portal fields, then when it called an update for an user some information was lost because dashboard receives the key with empty value.

Related Issue

https://tyktech.atlassian.net/browse/TT-4275

Motivation and Context

Provide consistency with the data

How This Has Been Tested

• Enabled MultiAPI Subscriptions in dev portal
• Created 2 apis with authentication token as authentication method
• Created one policy for each api
• Exposed the api in the catalog using the policies created previously
• Ran TIB as standalone app
• Created a profile to be used to SSO dev portal, it looks like:

{
  "ID": "ldap-for-sso-dev-portal",
  "Name": "ldap-for-sso-dev-portal",
  "OrgID": "5e2091c4d4aefce60c04fb92",
  "ActionType": "GenerateOrLoginDeveloperProfile",
  "MatchedPolicyID": "",
  "Type": "passthrough",
  "ProviderName": "ADProvider",
  "ProviderConfig": {
    "FailureRedirect": "http://tyk-portal:3000/login",
    "LDAPAttributes": [],
    "LDAPPort": "389",
    "LDAPServer": "ldap.forumsys.com",
    "LDAPUserDN": "cn=*USERNAME*,dc=example,dc=com"
  },
  "IdentityHandlerConfig": {
    "DashboardCredential": "b72f2d7713b34cdb643f7fefcc1eb8c8"
  },
  "ReturnURL": "http://tyk-portal:3000/sso/",
}

• Login to dev portal (it doesnt matter how, if with sso or user/password)
• Created the key for both apis
• Check the database, look in portal_developers collection your dev, then check keys, you will see your key and inside that 2 elements that basically are the relations
• Now I request the nonce using:

curl --location --request POST 'tyk-dashboard:3010/auth/ldap-for-sso-dev-portal/ADProvider' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'username=read-only-admin' \
--data-urlencode 'password=password'

• The response should be with status 301 (Moved Permanently), then copy the value for the header Location and paste it in the browser
• Go and check again the database...the key should have 2 elements
• For more details on how to test refer to https://tyktech.atlassian.net/browse/TT-4275?focusedCommentId=20929

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Refactoring or add test (improvements in base code or adds test coverage to functionality)

Checklist

• Make sure you are requesting to pull a topic/feature/bugfix branch (right side). If pulling from your own
  fork, don't request your master!
• Make sure you are making a pull request against the master branch (left side). Also, you should start
  your branch off our latest master.
• My change requires a change to the documentation.
  • If you've changed APIs, describe what needs to be updated in the documentation.
  • If new config option added, ensure that it can be set via ENV variable
• I have updated the documentation accordingly.
• Modules and vendor dependencies have been updated; run go mod tidy && go mod vendor
• When updating library version must provide reason/explanation for this update.
• I have added tests to cover my changes.
• All new and existing tests passed.
• Check your code additions will not fail linting checks:
  • go fmt -s
  • go vet

[sredxny]

@furkansenharputlu hi, I see this id to be bson.ObjectId, so am wondering if this will be an issue when dashboard use an SQL database.

[gregdelhon]

LGTM

[sredxny]

applied to release-1.2 as well