Using companys' proxy with lseg-data package

Hi !
In order to use the lseg-data Python package, I've fiddled in the GitHub standard package to try and open a session. However I am getting an error that obviously says that I need proxy authentication to actually test it properly (the error is quite clear).
I am setting the proxy settings in pip.ini for example if I want to download packages through pip, or in the settings before using the requests package. So I was wondering if it is possible to achieve the same with this package ? I want to specify username/password/proxyurl/proxyport.
Hope I was clear !
Regards,
Answers
-
Hello @Jugadorwc3
Are you using the Desktop Session or Platform Session?
If you are using the Desktop Session
The library connects and consumes data from the LSEG Workspace platform. The LSEG Workspace desktop application integrates the API proxy that acts as an interface between the Data library and the Workspace Platform. For this reason, the Workspace application must be running when you use the Data library with Desktop Session.
If you are using the Platform Session
The library connects and consumes data from the LSEG Delivery Platform over network. If your organization needs HTTP Proxy authentication to access an internet, you can check an accept answer on this StackExchange page about how to set HTTP Proxy using OS Environment Variable.
I hope this helps.
0 -
Hi Wasin,
Thank you for the quick reply. I am using a Desktop Session. The Workspace application is running in the background and I can fetch various data from the desktop application.
I have created an app key that is specified in the config file, and upon trying to open a session, I am met with an HTTP 407 error (Proxy Authentication required).
Hope this can help clear things out !
Regards,
0 -
Typically, a proxy is not required when connecting to a Desktop session because the library connects localhost. You may set the NO_PROXY environment before opening a desktop session.
import os
os.environ['NO_PROXY'] = 'localhost'0 -
Hello @Jugadorwc3
The library needs to connect to the Workspace desktop application (API Proxy) via localhost. Your organization might have a network policy that blocks access to a localhost.
I suggest you try my colleague suggestion above, or contact your local IT network team to help you check if there a network policy that blocks a connection to Workspace desktop application.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 37 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 697 Datastream
- 1.5K DSS
- 632 Eikon COM
- 5.2K Eikon Data APIs
- 12 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 4 Trading API
- 2.9K Elektron
- 1.4K EMA
- 256 ETA
- 563 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 281 Open PermID
- 46 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 749 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 123 Open DACS
- 1.1K RFA
- 107 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 96 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛