Details

    • Type: Bug
    • Status: Closed
    • Resolution: Fixed
    • Affects Version/s: 7.0.0 M3
    • Fix Version/s: 7.0.0 M2
    • Component/s: Staging
    • Labels:

      Description

      When remote publishing the following error message appears many times in the console

      19:43:12,220 ERROR [liferay/background_task-1][HttpPrincipal:55] com.liferay.portal.PwdEncryptorException: Unable to encrypt blank password
      com.liferay.portal.PwdEncryptorException: Unable to encrypt blank password
              at com.liferay.portal.security.pwd.BasePasswordEncryptor.encrypt(BasePasswordEncryptor.java:32)
              at com.liferay.portal.security.pwd.PasswordEncryptorUtil.encrypt(PasswordEncryptorUtil.java:99)
              at com.liferay.portal.security.pwd.PasswordEncryptorUtil.encrypt(PasswordEncryptorUtil.java:81)
              at com.liferay.portal.security.pwd.PasswordEncryptorUtil.encrypt(PasswordEncryptorUtil.java:67)
              at com.liferay.portal.security.auth.HttpPrincipal.<init>(HttpPrincipal.java:52)
              at com.liferay.portal.security.auth.HttpPrincipal.<init>(HttpPrincipal.java:30)
              at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
              at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
              at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
              at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
              at java.lang.Class.newInstance(Class.java:374)
              at com.liferay.portal.json.jabsorb.serializer.LiferaySerializer.unmarshall(LiferaySerializer.java:271)
              at org.jabsorb.JSONSerializer.unmarshall(JSONSerializer.java:692)
              at com.liferay.portal.json.jabsorb.serializer.LiferayJSONSerializer.unmarshall(LiferayJSONSerializer.java:50)
              at org.jabsorb.serializer.impl.MapSerializer.unmarshall(MapSerializer.java:265)
              at org.jabsorb.JSONSerializer.unmarshall(JSONSerializer.java:692)
              at com.liferay.portal.json.jabsorb.serializer.LiferayJSONSerializer.unmarshall(LiferayJSONSerializer.java:50)
              at org.jabsorb.JSONSerializer.fromJSON(JSONSerializer.java:262)
              at com.liferay.portal.json.JSONFactoryImpl.deserialize(JSONFactoryImpl.java:181)
              at com.liferay.portal.kernel.json.JSONFactoryUtil.deserialize(JSONFactoryUtil.java:89)
              at com.liferay.portal.model.impl.BackgroundTaskImpl.getTaskContextMap(BackgroundTaskImpl.java:155)
              at com.liferay.portal.lar.backgroundtask.BaseStagingBackgroundTaskExecutor.markBackgroundTask(BaseStagingBackgroundTaskExecutor.java:76)
              at com.liferay.portal.lar.backgroundtask.LayoutRemoteStagingBackgroundTaskExecutor.execute(LayoutRemoteStagingBackgroundTaskExecutor.java:153)
              at com.liferay.portal.kernel.backgroundtask.SerialBackgroundTaskExecutor.execute(SerialBackgroundTaskExecutor.java:56)
              at com.liferay.portal.backgroundtask.messaging.BackgroundTaskMessageListener.doReceive(BackgroundTaskMessageListener.java:110)
              at com.liferay.portal.kernel.messaging.BaseMessageListener.receive(BaseMessageListener.java:26)
              at com.liferay.portal.kernel.messaging.InvokerMessageListener.receive(InvokerMessageListener.java:72)
              at com.liferay.portal.kernel.messaging.ParallelDestination$1.run(ParallelDestination.java:71)
              at com.liferay.portal.kernel.concurrent.ThreadPoolExecutor$WorkerTask._runTask(ThreadPoolExecutor.java:728)
              at com.liferay.portal.kernel.concurrent.ThreadPoolExecutor$WorkerTask.run(ThreadPoolExecutor.java:639)
              at java.lang.Thread.run(Thread.java:745)
      
      

      this is because a new HttpPrincipal is created using no parameters for the arguments. Using new HttpPrincilap() or HttpPrincipal(string url) calls another constructor but null is used for the password. Null cannot be encrypted so the error message is thrown.

      NOTE: this does not prevent staging from completing, it just prints off a lot of extraneous error messages.

        Attachments

          Activity

            People

            • Assignee:
              mark.jin Mark Jin (Inactive)
              Reporter:
              andrew.betts Andrew Betts
              Participants of an Issue:
              Recent user:
              Esther Sanz
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Days since last comment:
                4 years, 29 weeks, 3 days ago