Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
User Experience
Lawson Smart Office
Installation Point and Certificate issue
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Wayne Willis
Past 24 Hours:
1
Prev. 24 Hours:
1
Overall:
5190
People Online:
Visitors:
259
Members:
0
Total:
259
Online Now:
New Topics
S3 Customization/Development
Cobol - Extract Current Time
4/24/2024 7:21 PM
How do you extract just the Current System Time in
Lawson Landmark
LPL INSTR Functions
4/5/2024 8:32 PM
I'm writing a simple report using the Create R
Infor SCM
Translating 856 to get the ~ REF^CN^ field
4/3/2024 8:24 PM
We are trying to get the tracking number which is
IPA/ProcessFlow
Sample XML file create Flow
4/3/2024 3:43 PM
Hello everyone, I am new to creating XML files
Lawson S3 HR/Payroll/Benefits
bn105 error message
3/26/2024 6:40 PM
I need to change some of the set ups in our Life I
IPA/ProcessFlow
IPA executing Job
3/13/2024 7:08 PM
New to the IPA world and was wondering, can an IPA
Lawson S3 HR/Payroll/Benefits
Life Age Reduction on benefits plans
3/12/2024 7:15 PM
For our optional life we have an age based coverag
Lawson S3 HR/Payroll/Benefits
BN53.1 Add-In
3/7/2024 3:31 PM
We are migrating to Solstice. They require a
Lawson Business Intelligence/Reporting/Crystal
Domain Name Change
3/5/2024 7:45 PM
Our domain name needs to change and was hoping I c
S3 Customization/Development
Cobol calling Shell Script
2/29/2024 1:27 PM
Has anyone created or modified a Lawson Cobol prog
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3288
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1351
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
Lawson Smart Office
Installation Point and Certificate issue
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
Roger French
Veteran Member
Posts: 545
8/11/2011 11:05 AM
Trying to install a new installation point on LS0 9.1.3. LifeCycle Manager, Grid, Webservices installed and running. LSO Server is running too.
I exported the server info to create the .jadeinstall file
I have a paid-for certificate that has been inserted into the proper key stores on the server and stored within IIS. It is a p7k and also I have a cer version.
When I try to create the installation point using SignTool, and link up the certificate to the installation point I am getting the pop up error "Unable to sign installation, Cannot find the original signer" as well as some other crypto string output.
Has anyone seen this type of message before? If so what did you do? I can't find any
documentation within Lawson and I am leaning that it is a certificate issue.
Thank you in advance,
Roger
Eklind
Veteran Member
Posts: 38
9/26/2011 7:49 AM
ClickOnce requires that all certificates in the cerificate chain is put in the trusted root certificate store. If you have bought a certificate which does not have the root certificate as issuer you need to add those certifcate between your certificate and the root certofocate into the trusted root store.
But what is the reason for using a bought code signinig certificate? If you will expose the installation point over internet it makes sence, but if only using it internally it is probably better to create a self-signed certificate with the Sign Tool.
/Rickard
Massimo Emilione
Advanced Member
Posts: 29
12/6/2011 9:53 PM
we created our own certificate and we got random errors with the import. I know I imported it into the trusted sites, but it did not work, we eventually let signtool create its own certificate. Everything is on our network internally.
Eklind
Veteran Member
Posts: 38
12/7/2011 9:15 AM
Massimo, I am not sure I understand what you try to achieve. The signtool can only produce a code signing certificate and have nothing to to with the communication (HTTPS/SSL).
Have a look at my posts in this thread
https://www.lawsonguru.co...afpg/2/Default.aspx,
ecpecially the one I posted December 2.
Massimo Emilione
Advanced Member
Posts: 29
2/7/2012 7:57 PM
Yes, this took a while to work out. There is a lot of signing occurring here.
You have to sign the install as well as have a working certificate to install into LCM so that users do not have to install the certificate. We are now using a CA certificate that is installed in LCM so that our users no longer have to install the certificate from
https://FQDN:19006/LSO
JimMNH
Veteran Member
Posts: 60
4/9/2012 6:35 PM
Use IE (run as administrator) to browse to the install point on your LSO server. Once there you should see a broken certificate. Install that and you should be fine. Created a KB for our folks here. You could try following this.
TO INSTALL AGAINST THE PRD LSO SERVER:
BEFORE STARTING: Normal LSO install MUST be done under the same account of the person/account that will be using LSO. This may require temporarily adding the user to the machine administrators group to complete the install. Administrator privileges are no longer required after the install has been completed.
(1) Make sure .NET Framework 4 is installed. The FULL install is required. Available under \\cityfile\Software\DotNet Framework 4 or online at
http://www.microsoft.com/...etails.aspx?id=17851
(2) Make sure the Lawson Grid self-signed certificate is installed on the client’s Trusted Root. To do this start IE as the machine Administrator (right click and select Run As Administrator). Navigate to https://{server}:19006 Click or left click on the certificate error (broken lock) and select "View Certificates". Go to the "Certification Path" tab and select "Lawson Grid" and choose to Install it to a specified location of Trusted Root.
(3) Once this is done you must restart the browser and point it again to the secure connection at https://{server}:19006 .. at this point the “golden lock” should appear indicating the encryption certificate is now trusted.
(4) You should now see a link to InstallationPoint/"Install Lawson Smart Office". You will need to install it logged in as the end user having machine administrator account privileges. Once installed you can launch it from the Start menu (Lawson folder), and login using AD credentials.
(5) Be sure to REMOVE machine administrator privileges from user after install if they did not have this priv before starting this install process.
BTW .. this dedicated install process isn't required using the URL shortcut I mention in my other post.
You are not authorized to post a reply.