The VS192 2-Port 4K DisplayPort Splitter is perfect for anyone who needs to send one source of DisplayPort high definition video to two or four DisplayPort displays. The VS192 can split and also expand DisplayPort audio/video signal on two or four DisplayPort monitors.
COURSE of the MONTH
9 days, 5 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Help on Single Sign On
Posted on 2013-01-08
Hi,
I configured and set up the SSO (single sign on) to access my Web server.
S.O: Linux
Web Server: Apache
Below the steps:
- Configured the Policy Domain and create a new Authentication Scheme on Oracle Access Manager
- Modify the http.conf file and add the rows:
ProxyPass /dbcenter/entry.php !
ProxyPass /dbcenter/login.php !
- Create the file: entry.php - login.php - myweb.php (see attached files)
Now when I try to connect at my portal web: http://10.11.12.33/myweb.php I get this warning:
Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/dbcenter/log
and then successfully entered
Have any idea how to avoid this warning?
entry.php
login.php
myweb.php
I configured and set up the SSO (single sign on) to access my Web server.
S.O: Linux
Web Server: Apache
Below the steps:
- Configured the Policy Domain and create a new Authentication Scheme on Oracle Access Manager
- Modify the http.conf file and add the rows:
ProxyPass /dbcenter/entry.php !
ProxyPass /dbcenter/login.php !
- Create the file: entry.php - login.php - myweb.php (see attached files)
Now when I try to connect at my portal web: http://10.11.12.33/myweb.php I get this warning:
Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/dbcenter/log
and then successfully entered
Have any idea how to avoid this warning?
entry.php
login.php
myweb.php
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2 Comments
Active today
This is nothing specific to SSO - this is a generic PHP / HTML problem. This happens because all web servers send back data in a very specific order:
1. HTTP Headers
2. Content
HTML belongs in the Content area, while any calls such as header() or setcookie() change information in the HTTP Headers area.
Once you send any Content, the web server assumes you are finished sending HTTP Headers, so it won't allow you to send any more HTTP Headers at that point.
There are several ways to fix this, but the easiest is probably just to add this line above your login.php script:
<?php ob_start(); ?>
This is called starting an output buffer (ob = output buffer). Basically, whenever it comes across any Content like HTML, it will not automatically output the HTML to the screen, but instead will put it into a hidden variable called an output buffer. Since the web server hasn't sent any Content back (because it's in the output buffer), it is still in the mode of expecting and accepting HTTP Header changes, so the setcookie() will work.
Now, there are ways to access and manipulate the contents of the output buffer, but you don't need to do anything more, since the output buffer will automatically dump whatever it has at the end if you don't do anything else.
Usually the proper way to get around this is to simply write code so that you do all your PHP processing first, and then display any HTML once you're done with PHP, but the ob_start() is a quick fix.
1. HTTP Headers
2. Content
HTML belongs in the Content area, while any calls such as header() or setcookie() change information in the HTTP Headers area.
Once you send any Content, the web server assumes you are finished sending HTTP Headers, so it won't allow you to send any more HTTP Headers at that point.
There are several ways to fix this, but the easiest is probably just to add this line above your login.php script:
<?php ob_start(); ?>
This is called starting an output buffer (ob = output buffer). Basically, whenever it comes across any Content like HTML, it will not automatically output the HTML to the screen, but instead will put it into a hidden variable called an output buffer. Since the web server hasn't sent any Content back (because it's in the output buffer), it is still in the mode of expecting and accepting HTTP Header changes, so the setcookie() will work.
Now, there are ways to access and manipulate the contents of the output buffer, but you don't need to do anything more, since the output buffer will automatically dump whatever it has at the end if you don't do anything else.
Usually the proper way to get around this is to simply write code so that you do all your PHP processing first, and then display any HTML once you're done with PHP, but the ob_start() is a quick fix.
You need to send header information prior to outputting anything to the browser window. Even stray white space at the end of a .php file can cause this error. you are having a problem here because you send stuff to the browser prior to the setcookie command. If you rearrange your login.oho file as follows, it should work for you.
<?php
$txtUserID = $_POST["IDUser"];
$token = $_POST["mytoken"];
$cookieValue = $token;
$cookieExpiration = 0;
$cookiePath = "/";
$cookieDomain = "gruppocattolica.it";
setcookie("mytoken",$cookieValue,$cookieExpiration,$cookiePath,$cookieDomain);
$input_arr =
array(
"txtUserID" => $txtUserID
);
?>
<html>
<head>
<script language="javascript">
<!--
function goSubmit() {
document.formric.submit();
}
//-->
</script>
</head>
<body onload="goSubmit();">
<form action="http://myportal.it/dbcenter/entry.php" method='POST' name='formric'>
<?php
foreach($input_arr as $key => $value)
echo "\t" . '<input type="hidden" name="' . $key . '" value="' . $value .'">' . "\n";
?>
</form>
</body>
</html>
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Have you tried to learn about Unicode, UTF-8, and multibyte text encoding and all the articles are just too "academic" or too technical? This article aims to make the whole topic easy for just about anyone to understand.
These days socially coordinated efforts have turned into a critical requirement for enterprises.
Explain concepts important to validation of email addresses with regular expressions. Applies to most languages/tools that uses regular expressions.
Consider email address RFCs:
Look at HTML5 form input element (with type=email) regex pattern:
T…
The viewer will learn how to look for a specific file type in a local or remote server directory using PHP.
Suggested Courses
Course of the Month9 days, 5 hours left to enroll
765 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.