Anyone knows where can I enable
"Billing address request is not enabled for merchant"
in sandbox environment?
Thanks
Darko
Please open a ticket to MTS technical team to help you on that.
Related
Our queries to Travelport support team:
We are facing some issues with the ticket API. An error occurred four
times, and the booking was not confirmed due to an "INVALID ND
LINKAGE" issue. as well as one more issue that is "Host error during
ticket issue-LINK UNAVBL/CALL VENDOR". In the auto ticketing scenario
(AirTicketing Req API) scenario, we got a "Host error" during ticket
issuance. We don't know the exact reason for this failure case
("INVALID ND LINKAGE"), so please guide us through what happened while
booking OID (OfficeId-PCC) travelport GDS.
Travelport Response from Travelport Support team Link:
Host error during ticket issue "INVALID ND LINKAGE" error implies
printer connections is not done yet. In uapi, you need to add printer
devices in uapi portal(aka admin portal) by yourself. I have seen
your printer device are not setup in prod admin portal.
You should be having your admin portal credentials with you if not,
please contact Travelport Account Manager to assist with the same,
they can raise request to access admin portal. We API Support, do not
have authorization to do this for you.
Please find the step to step guide to do the printer connections
https://support.travelport.com/webhelp/uapi/uAPI.htm#Getting_Started/AdminPortal/Printer_Connections.htm
When I access to my telegram-bot, after some time, it requires user authentication with the text:
"Stand by...
Hi there!
Before We Can Continue We Need To Verify That You're a REAL User"
When this message appears it seems session is closed, and the user can't receive Bot notifications, until user authenticates.
I can't understand why this authentication is required if I am storing each user telegram_id.
Your bot token might have exposed on git.
You need to change the token.
Instead of hard coding it in the code, pass it as an environment variable.
Just had the same issue!
I guess, someone scraped my bot-token from public repository and tried to steal my account. NEVER leave your bot-token in public rep!!!
Detailed description for others to find this thread:
Bot sent, what it was programmed to do and then
"Hi There!
Before We Can Continue We Need To Verify That You're A REAL User"
Telegram sent me login code -> I entered it (yeah, I'm dumb)
Bot printed
"Please reply with your 2FA (Two Factor Authentication / Two Step Verification) code"
then
"Timeout has been reached , pleaase try again."
(I like the pleAAse part, where you understand it was totally fake)
Telegram said it was
Device: Android
Location: Bulgaria (IP = 185.95.157.122)
I discovered what was wrong!
Lev Vasilyev answer made me think if somebody was able to get my bot_token. So, I changed it. And, the authentication message no longer appeared.
It´s important to get into telegram allowed devices, and delete not authorized accesses.
My bot has ""Stand by... Hi there! Before We Can Continue We Need To Verify That You're a REAL User" too.
When I proceed and send authentication code and sms from Telegram was received I had been authorized as Samsung Galaxy s20 5g from Seychelles ip adress which was not mine... This was very strange. If anybody had that experience please post your answer too. Maybe somebody had stolen my bot ...Sorry if my English not very correct and nice. I hope you understand.
I had the same problem, changed the Token and resolved the problem. I needed set the webhook again to work.
All replies are correct:
your token has been stolen and used by hackers, once you enter your credentials - you will see unknown sessions in your telegram.
Change token via BotFather and do not publish it in public places.
If you have already put your cred's to the telegram bot - you need to change the password immediatelly.
i would like implement OAuth 2.0 Client Credentials Flow (2-Legged), but as mentioned here : https://learn.microsoft.com/en-us/linkedin/shared/authentication/client-credentials-flow or https://developer.linkedin.com/docs/v2/oauth2-client-credentials-flow.
It's written : "Your application cannot access these APIs by default. Contact us to have your application granted permission to use this flow."
I don't find any contact (I tried linkedin support, they sent me on stack overflow..), does anyone has already done this setup ?
Thanks :)
I am in a similar boat and it seems that you will have to apply for further permissions on their partner programme page: https://developer.linkedin.com/partner-programs
I know this may be a bit of a late response but other developers stumbling across this may benefit from this answer.
HI,
I have given the server name, base dn, and the other reguired fields in /admin/settings/ldap/ldapauth/add and in advance configuration i have tested and it shows ldap authentication sucessfull. After this when i logout and enter the ldap username and password i am not able to login to the admin section.
I am not knowing whether i am doing any mistake in configuration or whats wrong why i am not able to authenticate the ldap users and login to the site.
Any help is greatly appreciated.
Have you tried the support queue for the module?
I am using built in Drupal 6 user module, fore user registration, forgot-your-password-emails and all that stuff.
When a notification is sent by e-mail for confirming reistration, resending passwords, etc, these are sent from a different e-mail address to the one I want.
I dont remember where I configured this setting, and cannot find where to change it again.
Can you help me? Thanks!
/admin/settings/site-information
Email address field.
Cheers!