This is not a limitation, its working as intended. The reason why PCS admins are not given an option to create SSO policy when exclusively using WSAM, JSAM or NC is because the traffic is not intermediated by the PCS Content Intermediation Engine (CIE).
When traffic does not go through the CIE PCS does not initiate a request to the backend server, the clients request is directly passed to the backend server.
Although the traffic is securely passing through PCS over an SSL session the server will still receive connection requests as if coming from the end client directly.
Hence an SSO policy created cannot be applied to these resources.
Currently SSO policy only applies to Web and File server resources.
For more information on CIE please refer to
Content Intermediation Engine
