expect4j.level = ALL
Solaris Connector
Identity connector for Solaris servers, possibly usable for other UNIX-like servers.
Functionality | stable |
Development status | abandoned (no longer developed or maintained, legacy code) |
Support status | unsupported |
Origin | ICF |
Support provided by | |
Target systems | Solaris servers, possibly also other Unix systems. |
Protocol | SSH/Telnet |
Source code | https://github.com/Evolveum/openicf/tree/master/connectors/java/solaris |
Capabilities and Features
Provisioning |
YES |
|
---|---|---|
Live Synchronization |
NO |
|
Password |
YES |
|
Activation |
YES |
|
|
YES |
|
|
YES |
History
This is mostly the original Sun ICF Solaris connector. It was extended for Linux use by Evolveum.
Version | Origin | Binary | Sources | Build Date | Description |
---|---|---|---|---|---|
1.1.0.e6322d |
OpenICF development version, built and tested by Evolveum |
OpenICF: solaris-connector-1.1.1.x-dev branch, revision 6322 |
Feb 2013 |
Solaris well tested, Linux slightly tested. There may be problems with sudo authorization. |
|
1.1.0.e6327d |
OpenICF development version, built and tested by Evolveum |
OpenICF: solaris-connector-1.1.1.x-dev branch, revision 6327 |
Feb 2013 |
Works well |
|
1.1.0.em13 |
OpenICF Evolveum version |
Evolveum OpenICF, revision emark-13-gd1b4de0 |
15 Aug 2013 |
Works well |
|
1.1.0.em77 |
OpenICF Evolveum version |
Evolveum OpenICF, revision emark-77-gbbe5fa6 |
Oct 2013 |
Somehow tested. |
Documentation
Patterns
The connectors works by matching patterns of the input that it receives from the Telnet/SSH channel.
Therefore also some of the configuration parameters are patterns. Especially the expected prompt configuration parameters |
Troubleshooting
Enable Logging
Set appropriate logger in midPoint:
Logger class name | |
---|---|
|
Connector functions |
|
SSH connection details (logs from the underlying JSch library) |
|
Sent and received data, pattern matching (logs from the underlying Expect4j library, see also a note below) |
The connector is using Expect4j library to do most functions.
The logging of the connector itself should be enough for normal troubleshooting (e.g. it displays every send and received command).
But for some problems a finer logging is needed.
Unfortunately the Expect4j is using obsolete java.util.logging (JUL) framework that does not work well with ICF.
Yet there is a workaround for this. Use the following line in logging.properties
file to enable Expect4j logging: