Template sign operations write the following debug output to console.log.
This is misleading information without any context of database and not useful.
It looks like leftover debugging which should be removed.
It is also filling up the log if you sign many databases with no need or relevance for an admin due to the missing context.
There is also no problem this debug helps to solve. It just looks like leftover debug information.
console_localhost_2024_02_29@09_52_52.log:[001590:000009-00007F9C905C1640] Adding sign bit to item IconBitmap
console_localhost_2024_02_29@09_52_52.log:[001590:000009-00007F9C905C1640] Adding sign bit to item $TemplateModTime
console_localhost_2024_02_29@09_52_52.log:[001590:000009-00007F9C905C1640] Adding sign bit to item $TemplateServerName
console_localhost_2024_02_29@09_52_52.log:[001590:000009-00007F9C905C1640] Adding sign bit to item $TemplateFileName
console_localhost_2024_02_29@09_52_52.log:[001590:000009-00007F9C905C1640] Adding sign bit to item $LargeSummary
console_localhost_2024_02_29@09_52_52.log:[001590:000009-00007F9C905C1640] Adding sign bit to item $LaunchXPageRunOnServer
console_localhost_2024_02_29@09_52_52.log:[001590:000009-00007F9C905C1640] Adding sign bit to item $FlagsNoRefresh
console_localhost_2024_02_29@09_52_52.log:[001590:000009-00007F9C905C1640] Adding sign bit to item $LANGUAGE
console_localhost_2024_02_29@09_52_52.log:[001590:000009-00007F9C905C1640] Adding sign bit to item $DefaultLanguage
console_localhost_2024_02_29@09_52_52.log:[001590:000009-00007F9C905C1640] Adding sign bit to item $Daos
console_localhost_2024_02_29@09_52_52.log:[001590:000008-00007F9C906C3640] Adding sign bit to item $DefaultNavigator
console_localhost_2024_02_29@09_52_52.log:[001590:000008-00007F9C906C3640] Adding sign bit to item $DefaultFrameset
console_localhost_2024_02_29@09_52_52.log:[001590:000008-00007F9C906C3640] Adding sign bit to item $DefaultWebFrameset
console_localhost_2024_02_29@09_52_52.log:[001590:000008-00007F9C906C3640] Adding sign bit to item IconBitmap
console_localhost_2024_02_29@09_52_52.log:[001590:000008-00007F9C906C3640] Adding sign bit to item $LargeSummary
console_localhost_2024_02_29@09_52_52.log:[001590:000008-00007F9C906C3640] Adding sign bit to item $LaunchXPageRunOnServer
console_localhost_2024_02_29@09_52_52.log:[001590:000008-00007F9C906C3640] Adding sign bit to item $FlagsNoRefresh
console_localhost_2024_02_29@09_52_52.log:[001590:000008-00007F9C906C3640] Adding sign bit to item $PIRCRefreshModTime
console_localhost_2024_02_29@09_52_52.log:[001590:000008-00007F9C906C3640] Adding sign bit to item $TemplateModTime
console_localhost_2024_02_29@09_52_52.log:[001590:000008-00007F9C906C3640] Adding sign bit to item $TemplateServerName
console_localhost_2024_02_29@09_52_52.log:[001590:000008-00007F9C906C3640] Adding sign bit to item $TemplateFileName
console_localhost_2024_02_29@09_52_52.log:[001590:000008-00007F9C906C3640] Adding sign bit to item $Daos
thanks for the comments and feedback. and for referencing the existing AHA idea.
To me it sounds like the debug messages should just be replaced by a proper signing message containing the database name. the signer should be the server name in all cases for your usecases.
I am not sure if that part could be used in any other way. but if there could be a different signer, also the signer name would be important.
by the way I am working on a signing tool, which can sign databases with any user.
- you can specify the Notes.ID with password
- load the id with user/password from IDVault (requires ID download count or automatic download)
- read it from a database using the API that is also used by $ShimmerID or if you only need one use the profile $ShimmerID
[ Daniel Nashed / https://blog.nashcom.de ]
Agreed - while technically useful in that this is the only output we get, it’d be vastly preferable to just have one “complete” message per DB and hide this behind a debug flag. I put in an idea a while back for the former: https://domino-ideas.hcltechsw.com/ideas/DOMINO-I-2408
I agree that we need some sort of message... Ideally when the signing is complete. I have learned that changes to one XPage requires 5 elements to be signed before it is ready for test ;-)
Also agree that the current messages lack context info. I don't need all of them - or if so they should ideally contain the name of the design element.
I second the idea but also the comment: remove the debug stuff but instead please give us a simple message that confirms the database has been signed. I exactly "use" these messages like the first commenter mentioned.
This is useful information when signing databases because you can then see when the sign process has completed.
For XPages developers signing all content with one user id (or the server id) is necessary for an XPages app that uses sessionAsSigner because if not signed by one id then the XPages app will fail to run code as signer (and the code will fail completely).
So I would like to keep the messages but it would enhance the message if the database path is added.