Web­Sphere 7: solu­tion to “pass­word is not set” while there is a pass­word set

I googled a lot re­gard­ing the er­ror mes­sage “pass­word is not set” when test­ing a data­source in Web­Sphere (7.0.0.21), but I did not find a solu­tion. A co-​worker fi­nally found a solu­tion (by ac­ci­dent?).

Prob­lem case

While hav­ing the ap­plic­a­tion JVMs run­ning, I cre­ated a new JAAS-​J2C au­then­tic­ator (in my case the same lo­gin but a dif­fer­ent pass­word), and changed the data­source to use the new au­then­tic­ator. I saved the con­fig and syn­chron­ized it. The files config/​cells/​cell­name/​nodes/​node­name/resources.xml and config/​cells/​cell­name/​se­cur­ity.xml showed that the changes ar­rived on the node. Test­ing the data­source con­nectiv­ity fails now with:

DSRA8201W: Data­Source Con­fig­ur­a­tion: DSRA8040I: Failed to con­nect to the Data­Source.  En­countered java.sql.SQLException: The ap­plic­a­tion server re­jec­ted the con­nec­tion. (Pass­word is not set.)DSRA0010E: SQL State = 08004, Er­ror Code = –99,999.

Re­start­ing the ap­plic­a­tion JVMs does not help.

Solu­tion

After stop­ping everything (ap­plic­a­tion JVMs, nodeagent and de­ploy­ment man­ager) and start­ing everything again, the con­nec­tion test of the data­source works dir­ectly as ex­pec­ted.

I have not tested if it is enough to just stop all ap­plic­a­tion JVMs on one node and the cor­res­p­ding nodeagent, or if I really have to stop the de­ploy­ment man­ager too.

StumbleUponXINGBalatarinBox.netDiggGoogle GmailNetvouzPlurkSiteJotTypePad PostYahoo BookmarksVKSlashdotPocketHacker NewsDiigoBuddyMarksRedditLinkedInBibSonomyBufferEmailHatenaLiveJournalNewsVinePrintViadeoYahoo MailAIMBitty BrowserCare2 NewsEvernoteMail.RuPrintFriendlyWaneloYahoo MessengerYoolinkWebnewsStumpediaProtopage BookmarksOdnoklassnikiMendeleyInstapaperFarkCiteULikeBlinklistAOL MailTwitterGoogle+PinterestTumblrAmazon Wish ListBlogMarksDZoneDeliciousFlipboardFolkdJamespotMeneameMixiOknotiziePushaSvejoSymbaloo FeedsWhatsAppYouMobdiHITTWordPressRediff MyPageOutlook.comMySpaceDesign FloatBlogger PostApp.netDiary.RuKindle ItNUjijSegnaloTuentiWykopTwiddlaSina WeiboPinboardNetlogLineGoogle BookmarksDiasporaBookmarks.frBaiduFacebookGoogle ClassroomKakaoQzoneSMSTelegramRenrenKnownYummlyShare/​Save

(Free)BSD in­side An­droid

Today I was look­ing into the Open­Source li­censes which are dis­played for An­droid (2.3.4). There are sev­eral files which come with a BSD li­cense.

Dur­ing look­ing at it, I no­ticed that the libm has the copy­right of sev­eral FreeBSD people. I did not had an in-​deep look if this is be­cause they took the FreeBSD libm, or if this is be­cause parts of the FreeBSD libm where ad­op­ted by other BSD pro­jects.

What I no­ticed is, that some spe­cial char­ac­ters are not dis­played cor­rectly. For ex­ample the name Dag-​Erling Smør­grav looks mangled in the dis­play of the li­cense in­side the phone (I hope it is dis­played bet­ter in my blog). His name is not the only prob­lem case, there are also other char­ac­ters which are not rendered as ex­pec­ted.

This does not really look pro­fes­sional.

One-​Time-​Passwords for Horde/​IMP?

I search a way to use one-​time–pass­words for Horde/​IMP on FreeBSD. I do not want to use PAM (local users on the ma­chine). Cur­rently I use the au­then­tic­a­tion via IMAP4 (link between the IMAP4-​server and post­fix via MySQL, to have the same PW for send­ing and re­ceiv­ing), and I ex­pect that not all users of Horde/​IMP will use OTP if avail­able, so the prob­lem case is not that easy. I can ima­gine a solu­tion which tries to au­then­tic­ate via OTP first, and if it suc­ceeds gets a pass­word for the lo­gin to the IMAP4 server. If the OTP-​auth fails, it could try the entered pass­word for the lo­gin to the IMAP4 server. Mi­grat­ing ex­ist­ing users to a new solu­tion can be done by telling them to enter the pass­word from the ma­chine of the per­son do­ing the mi­gra­tion. The solu­tion needs to auto­mat­ic­ally lo­gin to the IMAP4 server, en­ter­ing a pass­word for the IMAP4 server after the OTP-​login to Horde is not an op­tion.

Oh, yes, send­ing the pass­words over SSL is not an op­tion (that is already the only way to lo­gin there). The goals are to have

  • an easy to re­mem­ber pass­word for an OTP app on the mo­bile to gen­er­ate the real pass­word
  • the pass­word ex­pire fast, so that a stolen pass­word does not cause much harm
  • not the same login-​password for dif­fer­ent ser­vices (mail-​pw != jabber-​pw != user-​pw)

One-​Time-​Passwords for XMPP/​Jabber?

I search a way to use one-​time–pass­words for jabber/​XMPP (ejab­berd) on FreeBSD. I do not want to use PAM (local users on the ma­chine). Cur­rently I use the in­ternal au­then­tic­a­tion, and I ex­pect that not all users of the jab­ber server will use OTP if avail­able, so the prob­lem case is not that easy (mi­grat­ing ex­ist­ing users to a new solu­tion can be done by chan­ging the pass­word my­self and then telling them to change their pass­word, but there needs to be a way to let them change the non-​OTP pass­word).

I as­sume that OTP is not fore­seen in the XMPP pro­tocol, so where could I ask to have some­thing like that con­sidered as an ex­ten­sion (if such a place ex­ists at all)?

Oh, yes, send­ing the pass­words over SSL is not an op­tion (that is already the only way to lo­gin there). The goals are to have

  • an easy to re­mem­ber pass­word for an OTP app on the mo­bile to gen­er­ate the real pass­word
  • the pass­word ex­pire fast, so that a stolen pass­word does not cause much harm
  • not the same login-​password for dif­fer­ent ser­vices (mail-​pw != jabber-​pw != user-​pw)