[MGNLCAMPU-54] Can not push campaign after changes to superuser password Created: 10/Aug/16 Updated: 28/Feb/17 Resolved: 21/Feb/17 |
|
| Status: | Closed |
| Project: | Campaign Publisher |
| Component/s: | None |
| Affects Version/s: | 1.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Marcus Käppi | Assignee: | Oanh Thai Hoang |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 0.5d | ||
| Original Estimate: | 1d | ||
| Environment: |
Magnolia 5.4.8. |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
When trying to push content via campaign publisher it works initially. |
| Comments |
| Comment by Marcus Käppi [ 10/Aug/16 ] |
|
This error message is from the error log from the instance we are pushing from. 2016-08-10 13:43:02,022 | ERROR | http-nio-10.0.2.15-41680-exec-2 | info.magnolia.datatransfer.api.service.impl.DataTransferServiceImpl | Failed to push message<!DOCTYPE HTML> <form id="loginForm" action="" method="post" class="mgnl-form"> var username = document.getElementById('login-username') var password = document.getElementById('login-password') function removeErrorClass() { this.removeAttribute('class')} //username.onfocus = function(e){ e.preventDefault(); } username.onblur = removeErrorClass It is the instance that we are pushing to that the password for superuser is changed. |
| Comment by Viet Nguyen [ 11/Aug/16 ] |
|
Dear Marcus Käppi, We are glad to hearing from you and thanks for your reported issue. We also got the confirmation from your team regarding
We will start investigating the issue and provide you with any updated information as soon as we have. Have a good day! |
| Comment by Viet Nguyen [ 12/Aug/16 ] |
|
Dear Marcus, I tried to reproduce your issue on Magnolia 5.4.8 using Campaign Publisher module version 1.0 but the issue does not appear. Could you please help us with more information regarding how did you build your environment as well as specific configuration from your side so that we can reproduce the issue here and will help you on fixing it. Regards, |
| Comment by Marcus Käppi [ 07/Sep/16 ] |
|
Hi! The error is really there according to our users. They even published a video to show it. |
| Comment by Marcus Käppi [ 07/Sep/16 ] |
|
The Version is the latest 0.67 lightdev for telia and Magnolia 5.4.8. |
| Comment by Oanh Thai Hoang [ 08/Sep/16 ] |
|
Hi buf481 This is not a bug. This is a normal mechanism that works at very first release. The transferUser is configured at receiver instance to do some special tasks for system such as import task. Here is the configured path /modules/data-transfer-core/config/transferUser. In your case, at target author instance, please enter to /modules/data-transfer-core/config/transferUser and change password to superuser123 Regards, |
| Comment by Marcus Käppi [ 08/Sep/16 ] |
|
Thanks for the clarification. We can figure that the second request is more job to implement, but the Should I write a new jira for this? |
| Comment by Oanh Thai Hoang [ 08/Sep/16 ] |
|
Hi buf481 Thanks for your reply. Regarding option 2:
I think we can't base on role. Because this user is also used for authenticated in receiver instance, we can't use role to authenticate . By the way, the configured user does not need the role superuser, he just need role campaign-import Regarding option 1:
Our solution is adding new action in Data transfer app and we can click to action and configure user in there but the data of user still kept in old path /modules/data-transfer-core/config/transferUser and of course it will be encoded. I will create jira for option 1. Regards, |
| Comment by Oanh Thai Hoang [ 08/Sep/16 ] |
|
Ticket MGNLDATATR-123 has just been created. |
| Comment by Marcus Käppi [ 08/Sep/16 ] |
|
option with role-setting would be possible but requires design changes. |