Xerox FreeFlow Web Services Support & Software Betriebsanweisung
Integrations Guide
186
FreeFlow Web Services
Required Elements
Example
Description
one if the user does not exist.
•
CreateOrUpdate = Same as update, but create user if it
does not exist.
•
Delete = Permanently delete the user from Web Services.
•
Login = Log in without updating the user details.
If no value is given, user login is denied.
Multisite Compatibility
To support multisite compatibility:
1
Each site must have a different name. This limitation is not enforced by the GUI, since it is only
relevant when using LDAP or auto login.
2
You must add printproviderID=xxx to the url parameters
For example:
http://uniquesitename/iway?IID=2&printproviderid=6
Appendix
Using the Sample
The sample demonstrates SSO user and account creation and can be useful for demos and
authentication server development kick-off. Using the sample triggers a sample authentication server.
To use the provided sample:
To use the provided sample:
1
Log into:
HTTP
://
LOCALHOST
/N
EWS
W
AY
/T
EST
/A
UTO
L
OGIN
/
REQUESTLOGIN
.
ASP
?
2
Click
Use Get
or
Use Post
to run it. This will call a sample authentication server that will return this
xml file:
\NewEdition\IPanel\Db\AutoLogin\sample.xml
Troubleshooting
Below is a list of troubleshooting concepts that may help if something does not work.
•
Is your IIS working in debug mode (server side scripting checkbox)? If yes, then turn it off. The
authentication server request is performed using multi-threading, and debug mode does not support
this.
•
Is the application server up?
•
Are you running the sample from the same server as the application? If not, add the machineName
parameter to the url. For example:
http://rndprt002/newsway/test/autologin/requestlogin.asp?machineName=rndprt002
•
Is your configuration OK?
o
Did you configure the setup correctly? – is the authentication server URL correct?
o
Did you write the login URL correctly? IID ? printproviderID ?
o
Did you add the parameters that Web Services is supposed to forward to the authentication
server?
•
Is your authentication server OK?
•
Try simulating a call to your authentication server from the application
o
Did you get an XML in a browser? Do you see one in the logger?
o
Look at the XML – are any mandatory fields missing?