Hello Jacob -
You should be able to specify a URL parameter which includes embedded username and password credentials when configuring a Poll an External Website for XML inbound connector. However, you should be aware that doing poses a security risk, potentially exposing your credentials as the URL parameter is readable by anyone able to access your Server's REST endpoints ... specifically the GeoEvent endpoints on port 6180 (e.g. http://MyServer.MyDomain:6180/geoevent/rest).
The better approach would be to configure a new inbound connector using the HTTP‑BasicAuthentication transport and XML adapter. The transport and adapter are both available out of the box. Configuring a new connector does not require any SDK development. From within GeoEvent Manager, navigate to Site > GeoEvent > Connectors and click Create Connector. In a separate tab/window you can click to open any of the existing connectors to see how they have been configured and use them as an example.
If you do decide to use the out-of-the-box Poll an External Website for XML inbound connector, you may find that you need to URL encode the credentials you are embedding in the connector’s URL property.
The correct syntax, I believe, is https://<user>:<password>@app.site.com/
So, for example, you would URL encode your string as follows:
I tend to use http://meyerweb.com/eric/tools/dencoder/ when I need to interactively encode / decode URL strings.
Looking at the examples you posted … you may also find that you need to drop the @domain.com suffix from the URL. I am less sure about this than recommending you URL encode the value however. It may be that if you URL encode the value then you’ll be able to specify the fully-qualified credentials: user@domain.com:password@app.site.com
Hope this information helps -
RJ
