How to Parse XML in CakePHP

Hi all, this is a basic tutorial on how to parse  xml file in cakephp.
We all know that cakephp vastly utilizes the array concept in php. Here, I am going to explain you how to parse XML in CakePHP and convert it into an array.
Step1:
Get the XML Feed; for example you might be having an xml feed from a search engine or any other type of feed which is in xml. get the contents of the URL to do so, I’m going to create a function in my controller and utilize the XML helper.
create the function, say: parse_xml

function  parse_xml() {

App::import('Xml');
$raw_xml = file_get_contents("type your xml url here");
$parsed_xml = & new XML($raw_xml);

$parsed_xml = Set::reverse($parsed_xml);  // reversing the xml to array. this can be also used to convert an array to xml also.

return $parsed_xml;
}

That’s all.. everything done
to get the array to a variable

$xml_array = $this->parse_xml();

now try printing the array

echo "
";
print_r($xml_array)
die;

More Here

Courtesy:http://cakeleak.wordpress.com/2010/05/28/how-to-parse-xml-in-cakephp/

PHP / Java Integration

Introduction

Installing/Configuring

• Requirements
• Installation
• Runtime Configuration
• Resource Types

Predefined Constants

Java Servlet SAPI

Examples

• Java Example

Java Functions

• java_last_exception_clear — Clear last Java exception

More Here

Courtesy:http://www.php.net/manual/en/book.java.php

Lightweight Directory Access Protocol PHP

Introduction

Installing/Configuring

• Requirements
• Installation
• Runtime Configuration
• Resource Types

Predefined Constants

Using the PHP LDAP calls

Examples

• LDAP search example

LDAP Functions

• ldap_8859_to_t61 — Translate 8859 characters to t61 characters
• ldap_add — Add entries to LDAP directory
• ldap_bind — Bind to LDAP directory
• ldap_close — Alias of ldap_unbind
• ldap_compare — Compare value of attribute found in entry specified with DN
• ldap_connect — Connect to an LDAP server
• ldap_count_entries — Count the number of entries in a search
• ldap_delete — Delete an entry from a directory
• ldap_dn2ufn — Convert DN to User Friendly Naming format
• ldap_err2str — Convert LDAP error number into string error message
• ldap_errno — Return the LDAP error number of the last LDAP command
• ldap_error — Return the LDAP error message of the last LDAP command
• ldap_explode_dn — Splits DN into its component parts
• ldap_first_attribute — Return first attribute
• ldap_first_entry — Return first result id
• ldap_first_reference — Return first reference
• ldap_free_result — Free result memory
• ldap_get_attributes — Get attributes from a search result entry
• ldap_get_dn — Get the DN of a result entry
• ldap_get_entries — Get all result entries
• ldap_get_option — Get the current value for given option
• ldap_get_values_len — Get all binary values from a result entry
• ldap_get_values — Get all values from a result entry
• ldap_list — Single-level search
• ldap_mod_add — Add attribute values to current attributes
• ldap_mod_del — Delete attribute values from current attributes
• ldap_mod_replace — Replace attribute values with new ones
• ldap_modify — Modify an LDAP entry
• ldap_next_attribute — Get the next attribute in result
• ldap_next_entry — Get next result entry
• ldap_next_reference — Get next reference
• ldap_parse_reference — Extract information from reference entry
• ldap_parse_result — Extract information from result
• ldap_read — Read an entry

More Here

Courtesy:http://php.net/manual/en/book.ldap.php

Single Sign On with Pubcookie

A couple of months ago I had to find a solution to offer a single sign on service in a environment with PHP applications and Plone. I decided to use Pubcookie which is a good solution and has a good documentation although due to its small niche market its community is not very big.

According to SLOCCount most of the code is C and it has almost 50 thousand lines of code

Totals grouped by language (dominant language first):
ansic: 40864 (85.89%)
cpp: 4215 (8.86%)
sh: 2500 (5.25%)

Total Physical Source Lines of Code (SLOC) = 47,579

The documentation is available here, it is clear but from my point of view it lacks of a set of examples. The first time I installed pubcookie I was a bit confused, my first error was trying to install it without understand completely how it worked so my first advice is that you must understand how it works before. The key concept is to realize that the authentication and creation/validation of cookies is going to be performed by the pubcookie service. Your web applications won’t have to deal with this issues anymore.

Have a look at the diagram in the section How Pubcookie Works. In our example with Plone, PHP applications 

and Apache our agents would be:

• User-Agent, your browser
• Application Server, an apache module installed in the server which offers the web application. In our example we would have one for each web application
• Login Server, the service in charge of creating and delivering the important cookies and dealing with the user login form
• AuthN Server, in our example it could be offered by an LDAP server. The Login Server would deal with this authentication server. We only need one

Every time the user visits a protected url (by the apache module / application server) in one of the server applications, the application server finds out whether the users’ cookie is valid or not. Depending on the type of cookie the user provide, it (the application server) can forward the user to the login server or give him access as logged in. Once the application server ensures the user is a valid user with a valid cookie it passes the user to the web application using an apache header, this last step is very important from the security point of view. The web applications will blindly accept the user passed in that HTTP header so it must come only from localhost and only when the apache module checks the request comes from a valid user.

Hands on. Download it and install all the components (keyserver, keyclient, apache module ..), you will need to generate some keys used to sign and encrypt the cookies which are exchanged between the login server and the application server.

Once the daemons are running and the apache module is built, we can start setting up our Plone. The most important part is the configuration of the apache module, there is a Plone plugin (product) calledWebServerAuth that will do the rest of the job.

This is the important part of the apache configuration for our traffic over SSL:


ServerName www.example.com
SSLEngine On
SSLCertificateFile /etc/apache2/ssl/example.crt
SSLCertificateKeyFile /etc/apache2/ssl/example.key
# Prompt for authentication:

AuthType EXAMPLEAuth
PubcookieAppID zope
Require valid-user

# once we know the user is a valid user, we set the HTTP header with the username
RewriteEngine On
RewriteRule .* - [E=RU:%{REMOTE_USER}]
RequestHeader set X_REMOTE_USER %{RU}e

....


As I remarked before, the application (Plone in this case) will accept any user in the HTTP_X_REMOTE_USER header so we must avoid that header when our apache module for pubcookie is not checking it is sent by a valid user. That is, we remove this header unless it goes to the URL protected by the apache module (our application server).


...
RequestHeader unset X_REMOTE_USER
...

At this point, you would be able of using the single sign on service with Plone. The next step would be to add more web applications. If you don’t find a pubcookie plugin for your PHP application, you would have to edit the code to bypass the user and session verification in order to accept the user included in the HTTP_X_REMOTE_USER header.

Last but not least, thanks to cewing and erikrose in #plone IRC channel at freenode.net, they were very helpful 

More Here

Courtesy:http://sanacl.wordpress.com/2010/02/24/single-sign-on-with-pubcookie/