java - How to sign multiple JNLP application using Maven -


we use jnlp application business. actual use requires manual signing jars each release. leads having different certificates, expired certificates , on ..

we poc'ed maven automatically sign application maven jarsigner plugin.

now, best approach industrialize such process ? i'd have certificate shared among applications instead of recreating 1 everytime.

in particular:

  • is correct have certificate bunch of corporate applications, or shall consider having 1 per application ?

  • can imagine store certificate(s) dependencies (under business repo) , have both dev , release certificates fetched uppon build ? dev cert local build , release certificate release.

  • what flaws of such use ?

  • is there other/better solution ?

thanks answers.

there many ways solve problem, can share thoughts on subject.

a) assume different releases on different branches, in essence deal 1 release version @ time

b) assume per version, have different certificates per environment. per environment part can handled using maven profiles (http://maven.apache.org/guides/introduction/introduction-to-profiles.html), so...

whether have multiple or single certificate matter of preference. since provides level of trust between given user , given app judgment of risk versus maintainability. risk, in multiple apps same certificate gives higher exposure, malign exposure, , breach of 1 breach of all. may important certificates guard.. maintainability in apps follow same update cycle, , change 1 means change all.

so, coupling bit higher, risk harder , maintenance simpler.. if global enterprise acme inc risk higher if local enterprise icme inc. , other peoples data or money invite safest option available.

i see no reason why certificates cannot stored. either in repository or other safe repo or lying around. more interesting may private keys, can specify properties , have dev ones bound dev profile , release ones omitted, have provide them on command line.

assuming use maven jarsigner plugin, have ${my.keypass} , ${my.keystore}, , dev profile both properties set, , release profile keystore set.

last time used certificates in similar manner had: - set of individual components - in single repository - build single complete entity.

so sharing certificates easy takeaway. certificates except final prod in sourcecode repository certificate releases on secure server, had batch process few had access to.

as security compromises.. don't think ever encountered one, prepared :)


Comments

Popular posts from this blog

authentication - Mongodb revoke acccess to connect test database -

r - Update two sets of radiobuttons reactively - shiny -

ios - Realm over CoreData should I use NSFetchedResultController or a Dictionary? -