Skip to main content
M
meett9325076
Inspiring
November 24, 2020
Answered

Okta login form is not submitted in panel since Premiere Pro 2020 (14.4)

  • November 24, 2020
  • 3 replies
  • 1175 views

Okta login form is not submitted in panel since Premiere Pro 2020 (14.4)

 

Steps to reproduce:

  • Add below parameters in manifest.xml:

 

 

<Parameter>--enable-nodejs</Parameter>
<Parameter>--mixed-context</Parameter>

 

 

  • Redirect to okta login page on panel load, refer below index.html:

 

 

<html xmlns="http://www.w3.org/1999/xhtml">
    <head>
        <script>
	    window.location.href = 'https://test.oktapreview.com/login/login.htm';
        </script>
    </head>
	
    <body></body>
</html>​

 

 

  • Enter any username and password and click on "Sign In" button

 

Actual Result: Nothing happen, the form is not submitted. There isn't any error in console
Expected Result: The form should be submitted

Note:

  • The okta login form is submitted till Premiere Pro 2020 (14.3) and broken since 14.4 version

 

Premiere Pro Version: 2020 (14.4)
Extension Type: Panel

Thanks & Regards,
Meet Tank

 

This topic has been closed for replies.
Correct answer meett9325076

Hello @sujai s 

The issue has been fixed in Premiere Pro 15.4 (CEP 11)

Thanks,
Meet

3 replies

M
meett9325076AuthorCorrect answer
Inspiring
August 13, 2021

Hello @sujai s 

The issue has been fixed in Premiere Pro 15.4 (CEP 11)

Thanks,
Meet

O
onesmallcog
Participant
March 26, 2021

Premiere: 15.0 (Build 41)

 

Since one of our customers has updated to the latest Premiere biuld our CEP panel is experiencing unexplained crashes. The symptom is the panel flashes white and then reloads. The same version of the panel works in 14.3.2 but fails in newer builds. The customer is accessing the machine on which Premiere is running remotely through Teradici PCoIP.

 

Looking at the CEP panel-specific debug log file:

"C:\Users\<user>\AppData\Local\Temp\CEPHtmlEngine10-PPRO-15.0.0-*.log"

I'm seeing:

[0326/143112.347:ERROR:bad_message.cc(27)] Terminating renderer for bad IPC message, reason 95
2021-03-26 14:31:12:354 : INFO CEPHTMLENGINE, RenderProcess terminated with status=2

 

So it appear the CEP engine is terminating for some reason. 

 

I have tried connecting the debugger and stepping through the code, but the issue seems to happen outside our code (when we return from a DOM event handler). I'm not seeing anything relevant in the debugger's console.

 

The issue only happens at this site, and only for some users, but for those users it happens consistently.

 

Because it's not occurring 'in' our code I'm not sure what additional information I can provide - but if anyone has any clues I've run out of ideas.

 

S
Adobe Employee
sujai s
Adobe Employee
March 25, 2021

Can you try using single context instead of multiple context and check if this resolved your problem? Else you can try disabling nodejs in just the iFrame that is doing the okta workflow.

M
meett9325076Author
Inspiring
March 25, 2021

@sujai s Thank you for looking into this.
We need to run the extension in mixed context only. This is working with mixed context till Premiere Pro 14.3, something has changed in Premiere Pro 14.4 (CEP 10)
There is no iframe in our case, we simply redirect to okta login page

Thanks,
Meet

S
Adobe Employee
sujai s
Adobe Employee
March 26, 2021

@meett9325076  I'm sorry, I don't understand this. Mixed context should be enabled only when you have iframes., otherwise this parameter is not needed at all. You please go though the docs for more details.

 

If no iframes, --mixed-context is really not needed.

If mixed context is needed for some specific reason, then please use disable-nodejs as explained in this section.

 

thanks

Sujai

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices