cancel
Showing results for 
Search instead for 
Did you mean: 
13 Replies
bmweaver1
New Member
New Member

Re: Trouble with template pools and authentication

Jump to solution

Xerox Connect Key Network Stored Scan template FIX

There are 2 things that have to be changed to the templates created by a system template

  • You have to add the login password using this format

string DocumentPath = "NAME OF THE NEW TEMPLATE";

     string UserNetworkFilingLoginName = "CMH\\XeroxLDAPReadOnly";

string UserNetworkFilingLoginID = "super secret PASSWORD";

 

  • You have to change the source of the in the template file from ”system” to template

enum_loginsource LoginSource = TEMPLATE;

 

This all worked On Firmware Version 072.060.165.14201

The templates will not appear when you refresh the folder unless the following properties attribute is set File is ready for archiving and allow this file to have contents indexed in addition to the file

two other considerations, the password is stored in plain text so the access rights to the template directory need to have rights to read it limited to just the Xerox Copier account with our “super secret password” and the administrator and information systems “IS user group”

Also these customized templates only seem to work on the Connect key 3655, and MAYBE other connect key devices, however the Work center 4265 non connect key does NOT like these templates. But the good news is that the WC4265 network templates work anyway and have no

0 Kudos
bmweaver1
New Member
New Member

Re: Trouble with template pools and authentication

Jump to solution

Xerox Connect Key Network Stored Scan template FIX

There are 2 things that have to be changed to the templates created by a system template

  • You have to add the login password using this format

string DocumentPath = "NAME OF THE NEW TEMPLATE";

     string UserNetworkFilingLoginName = "CMH\\XeroxLDAPReadOnly";

string UserNetworkFilingLoginID = "super secret PASSWORD";

 

  • You have to change the source of the in the template file from ”system” to template

enum_loginsource LoginSource = TEMPLATE;

 

This all worked On Firmware Version 072.060.165.14201

The templates will not appear when you refresh the folder unless the following properties attribute is set File is ready for archiving and allow this file to have contents indexed in addition to the file

two other considerations, the password is stored in plain text so the access rights to the template directory need to have rights to read it limited to just the Xerox Copier account with our “super secret password” and the administrator and information systems “IS user group”

Also these customized templates only seem to work on the Connect key 3655, and MAYBE other connect key devices, however the Work center 4265 non connect key does NOT like these templates. But the good news is that the WC4265 network templates work anyway and have no

 

PS no spaces in template names

0 Kudos
PaulG03641-GIS
Technical Escalation User
Technical Escalation User

Re: Trouble with template pools and authentication

Jump to solution

I have found a Solution that worked me using an Alternate repository, instead of the Default repository when initially creating your template/XST file.Let me know if this works for you, and I will post to the other threads reporting the same issue.

 

For those that have never setup a Template Pool

1. Go into the Template Pool Setup and configure it so that machines will pull templates from a designated share/folder

2. Create an Alternate Repository pointed at the share/folder where you will have the subfolders in which to scan to.

3. Create a standard scan template, that uses the Alternate Repository and be sure the Job Log is turned on

4. Scan to the folder and open the XST file for editing

5. Edit the line that says boolean SuppressJobLog = False to be "TRUE"

6. Save file a change file name to reflect what you want displayed on the copier.

7. Move this file to your Template Pool share/folder

8. Select Update/Refresh templates on either the control panel or on web interface

8. Test a Scan -- and say badabing ;-)

 

Note: You will need to enable the Template Pool Setup and create an Alternate on each copier that will utilize the Template Pool. The Alternate NAME is not required to be the same on each copier for it to work -- it just needs to have one created.

0 Kudos

Re: Trouble with template pools and authentication

Jump to solution

I found the solution.  In the section below is a variable which can take at least four values.

 

[service xrx_svc_file]

file_1{

* enum_filingpolicy DocumentFilingPolicy = NEW_AUTO_GENERATE;

.

.

.

boolean ServerValidationReq = FALSE;

enum_loginsource LoginSource = TEMPLATE; <-----------------------

boolean DocumentDirectoryXSM = TRUE;

ref_invocation OutputDocument = xrx_document:doc_1;

}(XRX_STATUS_COMPLETED)

end

 

The values I've been able to find are:

  • NONE
  • SYSTEM
  • PROMPT_WHEN_REQUIRED
  • TEMPLATE

When the password is stored in the template, the value should be "TEMPLATE."

 

It works now.

 

 

Fabio
Valued Advisor
Valued Advisor

Re: Trouble with template pools and authentication

Jump to solution

some more info

 

Essentially if the path of the user template does not match the path in the default template it will prompt you for a user name and password. So essential every user template is going to have this problem, otherwise everyone would scan to the default and you would not need user templates.

You have to edit each .xst file to add have a username and password string.

string UserNetworkFilingLoginName = "your login name";
string UserNetworkFilingLoginID = "your password";

Open the .xst files (one at a time) in wordpad or notepad and add the above lines with the information in quotes filled in. As my example shows.

[service xrx_svc_file]
file_1{
* boolean ServiceEnabled = TRUE;
ref_invocation OutputDocument = XRX_DOCUMENT:doc_1;
string RepositoryName = "127.0.0.1";
string DocumentPath = "/cw_scan/data/system/public";
string RepositoryVolume = "";
string NDSNameContext = "";
string NDSTree = "";
enum_namespace FilingNameSpace = UNIX;
enum_filingprotocol FilingProtocol = FTP;
enum_filingpolicy DocumentFilingPolicy = NEW_AUTO_GENERATE;
}
End

Change it to this putting in the username and password.

[service xrx_svc_file]
file_1{
* boolean ServiceEnabled = TRUE;
ref_invocation OutputDocument = XRX_DOCUMENT:doc_1;
string RepositoryName = "127.0.0.1";
string DocumentPath = "/cw_scan/data/system/public";
string UserNetworkFilingLoginName = "your login name";
string UserNetworkFilingLoginID = "your password";
string RepositoryVolume = "";
string NDSNameContext = "";
string NDSTree = "";
enum_namespace FilingNameSpace = UNIX;
enum_filingprotocol FilingProtocol = FTP;
enum_filingpolicy DocumentFilingPolicy = NEW_AUTO_GENERATE;
}
end

Re: Trouble with template pools and authentication

Jump to solution

I spoke too soon.  No go.  After modifying the template, then logging in to the MFD and updating its templates, I attempted to scan a document.  It asked for authentication.  The key portion of the template looks like this (username and password fields scribbled to protect the guilty):

 

[service xrx_svc_file]

file_1{

* enum_filingpolicy DocumentFilingPolicy = NEW_AUTO_GENERATE;

* string RepositoryAlias = "Doc.IT";

* string DocumentPath = "My_Path";

string UserNetworkFilingLoginName = "OCR_account";

string UserNetworkFilingLoginID = "OCR_account_password";

enum_filingprotocol FilingProtocol = SMB;

string RepositoryName = "OCR-server:445";

string RepositoryVolume = "UserFolders";

string NDSTree = "";

string NDSNameContext = "";

boolean ServerValidationReq = FALSE;

enum_loginsource LoginSource = SYSTEM;

boolean DocumentDirectoryXSM = TRUE;

ref_invocation OutputDocument = xrx_document:doc_1;

}(XRX_STATUS_COMPLETED)

end

 

 

0 Kudos
Fabio
Valued Advisor
Valued Advisor

Re: Trouble with template pools and authentication

Jump to solution

google for the correct keywords :-)

 

actually came on this topic: 

 http://forum.support.xerox.com/t5/General-Information/Modify-xst-file/td-p/141617

0 Kudos

Re: Trouble with template pools and authentication

Jump to solution

How the heck did you find that!????? I've been looking for 30 minutes!

 

0 Kudos
Fabio
Valued Advisor
Valued Advisor

Re: Trouble with template pools and authentication

Jump to solution

ah , found it

 

here is an example : 

 

[service xrx_svc_file]
 file_1{
    * boolean ServiceEnabled = TRUE;
      ref_invocation OutputDocument = XRX_DOCUMENT:doc_1;
      string RepositoryName = "11.22.33.44";
      string DocumentPath = "/verne";
      string UserNetworkFilingLoginName = "scan";
      string UserNetworkFilingLoginID = "secret-pc-password-here";
      string RepositoryVolume = "";
      string NDSNameContext = "";
      string NDSTree = "";
      enum_namespace FilingNameSpace = UNIX;
      enum_filingprotocol FilingProtocol = FTP;
      enum_filingpolicy DocumentFilingPolicy = NEW_AUTO_GENERATE;

0 Kudos
Fabio
Valued Advisor
Valued Advisor

Re: Trouble with template pools and authentication

Jump to solution

just googled

 

try this for username

 

* string UserNetworkFilingLoginName = "d\\scanuser";

 

setup under the filling options , where the storage is filled in 

0 Kudos