Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Verified Answer
  • Replies reply
    1
  • Subscribers subscribers
    20
  • Views views
    96
  • Users 0 members are here
  • +1 person also asked this people also asked this
Related
Options

Retriveing email from GMAIL API and add to SMAX Service Request

The John Christie

We currently use CIT ro read email from GMAIL via Internet IMAP connector and insert that into SMAX. We have to use "Less secure apps' configuration on the malbox to be ble to access the email with user name and password.

Google will soon depricate "less secure apps' option and will break our CIT connector. 

This means that we will have to use a Google project and OATH2 to access the mailbox with token. CIT does not provide  a connector for this.

We are attempting to use SMAX integration Engine to connect to GMAIL endpoint (succesfully) using OATH2, BUT the body and attachments via the GMAIL API are only provided in base64 in theJSON payload

Looking to see if anyone has attempted this before or is there a method in the scenario rules to be able to decode the base64 data?

  • Verified Answer

    +1  

    Hi John,

    At present there is no capability to encrypt/decrypt base64 within the Integration Engine. This would need to be added to the Integration Engine.

    Could you raise an Idea on the Idea Exchange to get this functionality added to the Integration Engine.

    Thanks

    Dave

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.