# Authentication to Ignition OPC UA Server

**URL:** <https://forum.inductiveautomation.com/t/authentication-to-ignition-opc-ua-server/35502>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [June 10, 2020, 2:41pm UTC](https://forum.inductiveautomation.com/t/authentication-to-ignition-opc-ua-server/35502 "2020-06-10T14:41:23Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![mogundipe](https://avatars.discourse-cdn.com/v4/letter/m/7ba0ec/32.png) [@mogundipe](https://forum.inductiveautomation.com/u/mogundipe)\
**Post date:** [July 17, 2020, 12:55pm UTC](https://forum.inductiveautomation.com/t/authentication-to-ignition-opc-ua-server/35502/17 "2020-07-17T12:55:08Z")

</div>

> [@Error installing security token](https://forum.inductiveautomation.com/t/error-installing-security-token/35562/4):
>
> Okay, it’s what I suggested. By default Ignition’s OPC UA server only accepts secured connections at `opc.tcp://10.122.220.204:62541` . Unsecured discovery services can be found running at `opc.tcp://10.122.220.204:62541/discovery` .
> 
> Some clients are defective and can’t handle this kind of setup. If that’s the case here, you change the configuration of Ignition’s server to allow `None,Basic256Sha256` for its security policies (and restart) then this client will probably be able to connect.

Changing the config of the server to allow 'None,Basic256Sha256' for the security policy got rid of my issue.

---

_[View the full topic](https://forum.inductiveautomation.com/t/authentication-to-ignition-opc-ua-server/35502)._