Exposing User properties in remote portlet?

I am somewhat familiar in firing methods and such with the EDK's. But exposing some of the user meta data (i.e. Email, Title, etc) is proving to be more difficult. Any help in the right direction?
vr, Rich

Judging by the fact that you want Email, Title etc, I'd say you want User Info settings, not user properties (the former are user settings while the latter are objects themselves associated with the user).
In VB:
DimptContextAsPlumtree.Remote.Portlet.IPortletContextDimptRequestAsPlumtree.Remote.Portlet.IPortletRequestptContext= Plumtree.Remote.Portlet.PortletContextFactory.CreatePortletContext(Request, Response)ptRequest= ptContext.GetRequest()DimvalueAsStringvalue= ptRequest.GetSettingValue(Plumtree.Remote.Portlet.SettingType.UserInfo, "Title")
Make sure that user info settings you are interested in are selected in the User Information section for your web service and note their mapped name in the User Profile Manager.
Ruslan.

Similar Messages

Expose JSF app as a remote portlet on OAS 10.1.3.1

Hello,
We have a requirement to expose our JSF app as a remote portlet via WSRP.
Our production platform is OAS 10.1.3.1 SOA and we are using JDeveloper 10.1.3.1 for the development.
We are new to the portal technologies, but what we understood reading the docs is that we must use WEB Center framework to expose the JSF app as a remote portlet. Is this correct?
Also, how can we install the WEB Center to our OAS 10.1.3.1 SOA ?
thank you

Hi, to expose your JSF application as a portlet you wil need to use the WebCenter Portlet Bridge, this is our implementation of JSR 301:
- http://download.oracle.com/docs/cd/B32110_01/webcenter.1013/b31074/jpsdg_java_adv.htm#BABBFDHA
Oracle WebCenter was released with OracleAS 10.1.3.2 and requires a minimum of ADF 10.1.3.2 runtime libraries, you can either deploy the required ADF Runtime Libraries to your 10.1.3.1 OC4J or upgrade to OracleAS 10.1.3.3 which is the latest release. You can find more information here:
- http://www.oracle.com/technology/software/products/jdev/htdocs/adfinstaller.html
Cheers,
Mick.

Remote portlet failing after upgrading to 6.5 and SQL Server to 2005

we are upgrading our environment from 6.1 mp1 to 6.5 in the process we upgraded our sql server from 2000 version to 2005.After the database upgrade all our remote custom portlet developed using API's to query the database to get user properties or documents name in KD is failing at the point where it try’s to make the call to the database.
We are getting following error on all the portlets result page “The underlying connection was closed: The server committed an HTTP protocol violation. “
For example for user search portlet its fails at this line
IPortalSearchRequest searchRequest = searchFactory.CreatePortalSearchRequest();
Any Ideas??
Edited by spinto at 06/11/2008 7:02 AM
Edited by spinto at 06/11/2008 11:59 AM

You had 6.1 MP1 running on SQL 2000? If you pulled off that sql magic, this issue should be peanuts. ;-)
Seriously, though, when we went from 6.1 to 6.1 MP1, all of our apps using the native API's IPTSearchRequest broke. Notice I said 'IPT' not just 'I' - again, I'm talking about the native api, not the remote. Though come to think of it, the remote search api calls may have broken, too. That was the whole reason we put off the MP1 upgrade - it broke the search in all our tests. I don't think it was until the patch 1 for MP1 came out that we moved forward.
Enough of my yapping, our fix for the native api apps - those using IPTSearchRequest - was to simply recompile the apps using the MP1 assemblies. Whatever the handful of assemblies you may have referenced in your project to get the native api working, just change their ref path to the newer MP1 assemblies - or in your case the new 6.5 versions. That fixed us right up.
Edited by tjannotta at 06/12/2008 7:36 AM

Returning to different community pages from remote portlet

Hi,
I'm trying to determine the options available if we'd like to a remote portlet on one community page to return to a different page within the community on post back. We're able to dynamically build out a redirect string using parts of the request's hostpage properties, but we know that the page id of the community will probably change between different environments (dev/staging/live). I understand that pages don't have UUIDs so that's out.I'm sure there are some kludgey workarounds like keeping track of the different pageIDs as preferences or an external file, but we'd like to do this the "right" way if possible so we don't have to separately maintain that info.
Any help is appreciated, thanks!

hi,
i don't think producer can access consumer's backing contexts.
but you can use backing files on the proxy portlets and retrieve desktop, page names in the backing file and pass the data to producer using custom data transfer technique. For further info, pl. refer to the below link.
http://edocs.bea.com/wlp/docs81/wsrp/custxfer.html
-sampath

Order of execution of named method user properties and server script

Dear All,
If for a Custom method on an applet, we have scripts in WebApplet_preinvokemethod and WebApplet_invokemethod and also for the same Custom method we have applet Named Method user properties and BC Named Method user properties, what will be the order of execution of these scripts and Named Method user properties??

The Private Event Submission sample portlet shows how to achieve this. It is part of the PDK download.
Peter

ALUI-Create Web Service - Remote Portlet Error 401:Unauthorized

I have some problems during user ALUI(AquaLogic User Interaction 6.1).
I created a Web Service - Remote Portlet,then set value of Basic Authentication Settings is "User's Basic Authentication Information". When related remote server refer to tomcat5.5,the Web Service - Remote Portlet is fine to run,but not when the related remote server refer to weblogic9.2.
When value of Basic Authentication Settings is "Use Remote Server Basic Authentication Information", related remote server refer to weblogic9.2 or tomcate5.5, the portlet is fine.
error detail:
Error
sso Portlet cannot be displayed because the remote server returned an invalid HTTP response code.
We recommend:
• Refresh sso Portlet
• Accessing this portlet at a later time.
• Contacting your portal administrator if problems persist.
Detailed error information
• Response status: 401
• Response body:
Error 401--Unauthorized
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.2 401 Unauthorized
The request requires user authentication. The response MUST include a WWW-Authenticate header field (section 14.46) containing a challenge applicable to the requested resource. The client MAY repeat the request with a suitable Authorization header field (section 14.8). If the request already included Authorization credentials, then the 401 response indicates that authorization has been refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has already attempted authentication at least once, then the user SHOULD be presented the entity that was given in the response, since that entity MAY include relevant diagnostic information. HTTP access authentication is explained in section 11.

How to configure remote server to accept authorization header?
I set value of Basic Authentication Settings is "User's Basic Authentication Information" because the Web Service - Remote Portlet need to get the portal's login user infomation.If the value is "Use Remote Server Basic Authentication Information",the application is fine to run.
The follow is the way to get login user infomation.
IPortletContext portletContext = PortletContextFactory.createPortletContext(request, response);
ICredentialProvider cProvider = portletContext.getCredentialProvider();
String username = cProvider.getUsername();
String password = cProvider.getPassword();
Do you have other way to authenticate users?
Thanks.
Edited by: user2233298 on 2009-4-22 下午8:25

JSF app as a remote portlet on OAS 10.1.3.1

Hello,
We have a requirement to expose our JSF app as a remote portlet via WSRP.
Our production platform is OAS 10.1.3.1 SOA and we are using JDeveloper 10.1.3.1 for the development.
We are new to the portal technologies, but what we understood reading the docs is that we must use WEB Center framework to expose the JSF app as a remote portlet. Is this correct?
Also, how can we install the WEB Center to our OAS 10.1.3.1 SOA ?
thank you

Hi,
In one of our current projects we're using SOA Suite and WebCenter. For example, we're exposing a JSF page containing a custom-built human workflow tasklist as remote portlet.
We have installed a separate WebCenter AS 10.1.3.2.0 besides the AS SOA Suite. (See: http://www.oracle.com/technology/software/products/ias/htdocs/101320ws.html) and patched it to 10.1.3.3.0. For development we use JDeveloper 10.1.3.3.0 and its pre-configured WebCenter OC4J.
We had some issues with the JSF portlet-bridge and opened tar's, but these we're resolved by Oracle.
Regards, Ronald

User profile vs Remote Desktop Services Profile

On a Windows 2008 R2 Domain Controller, if you open properties of an user account, you'd see
a Profile Tab as well as Remote Desktop Services Profile Tab.
I found this very confusing, can any one tell be the key difference between those 2?
If I don't specify Remote Desktop Services Profile path, when I logon to Remote Desktop Server, it seems take user's
romaing profile.
Anyway, please advice.
Thank you.

Hi,
Thank you for posting in Windows Server Forum.
The profile tab of the user properties window allows you to configure user profile, logon scripts and home folder details for the user object. It is very useful when you have to allow your user access the same environment and data irrespective of the machine
he logs in from.
Active Directory User properties – Profile tab
Remote Desktop Services User Properties
You can specify a Remote Desktop Services-specific profile path and home folder for a user connecting to an RD Session Host server. This profile and home folder will only be used for Remote Desktop Services sessions. You should assign a separate profile for
Remote Desktop Services sessions because many of the common options that are stored in profiles, such as screen savers and animated menu affects, are not desirable when using Remote Desktop Services.
Manage User Profiles for Remote Desktop Services
http://technet.microsoft.com/en-us/library/cc742820.aspx
User Profiles on Windows Server 2008 R2 Remote Desktop Services
http://blogs.msdn.com/b/rds/archive/2009/06/02/user-profiles-on-windows-server-2008-r2-remote-desktop-services.aspx
Hope it helps!
Thanks.
Dharmesh Solanki

Timeout during a remote portlet request

I'm facing a problem on portal consuming a remote portlet on wlp 8.1 SP4/5.
We ask me to prevent a communication leak during a wsrp communication between me (the consumer) and a producer.
I have seen this parameter that can be add to my wsrp-producer-registry.xml :
connection-establishment-timeout-msecs
connection-timeout-msecs
This is a container way to change the parameter but what do you suggest to manage the error when it appears. Is their and error page on portlet ? in web.xml?
Thanks for any suggestion.
Yo.

In G6, we have provided a way for a remote portlet to grab the parameters from the URL. If you go to the user info page for the web service, you will see a new option: "Host Page URL Query String". If you check that box, the remote tier will get the full query string, as typed into the browser, as a user info parameter. You can then parse that query string and get any additional arguments that you have passed in.
We realize that this will not work in 5.x, which most of you use. Below you will find the code that you can put into your 5.0 portaluiinfrastructure.jar/dll to make the same change as what we did with G6. That way, if you write your portlets to this feature now, when you upgrade to G6 they will continue working and you shouldn't have to do any modifications to the portal UI.
Locate AppDataObject file, which should be in portaluiinfrastructure.statichelpers package. Find this function:
public static IPTState GetAppDataObject(int iCommunityID, int iPageID, int iGWParams, String strHostPageURI, AActivitySpace asOwner, boolean bResolveSecureBase)
It should be a pretty long function that adds all sorts of stuff to objAppDataObject. At the very end of this function, immediately before the log.Debug statements, add the following line of code:
//set the query string on UserInfoptSession.GetUserInfo().AddUserInfoSetting("HostPageQueryString", asOwner.GetCurrentHTTPRequest().GetQueryString());
Build and deploy a new portaluiinfrastructure.jar/dll according to instructions published on the dev center.
Start the portal, open the web service object corresponding to the portlet which should have access to query string parameters from the URL. On the User Info page, add user info setting name "HostPageQueryString". In your portlet, get the user info setting with that name - you will have the query string as entered in the browser.
Feel free to post in this thread if you encounter any difficulties with this approach.

Convert MyFolder in 4.5 to Remote Portlet in 5.0

We want to convert the native gadget "My Folders" in 4.5 to a remote Portlet in 5.0 as this native gadget has no longer been supported in 5.0. Has anyone done this? Any suggestions or good practive advices? We would also like to migrate the current "My Folders" user data to the 5.0 with the new gadgets. Thanks much!
Hao Pan ([email protected])

Your psychic - I looked at that yesterday because I opened the dbupgradetool.bat and it calls portalenv.bat which does this:
rem * Set PORTAL_HOME, CLASSPATH, and PATH
set PORTAL_HOME=%PT_HOME%\ptportal\6.1
set PATH=%PORTAL_HOME%\bin\native;%ICU_PATH%;%INXIGHT_PATH%;%OUTSIDEIN_PATH%;%PTHREADS_PATH%
set CLASSPATH=.;%PORTAL_HOME%\lib\java\portalapi.jar
set PT_JRE=%PT_HOME%\common\jre\1.4.2
Now I looked in my environment variables collection and I don't see CLASSPATH or PT_JRE. So I'm wondering if it ever even got to this point. I tried adding manually, but got the same error.
I think you're on to something and I'm going to look into this as a possible solution again. This has to be what it means.
To answer your question, yes my 6.1 portal comes up vanilla just fine when I open the portal config manager and point the db to the 6.1 db. Hmmm..as I type though, I'm thinking about my environment. I've tried the upgrade on a 4.5WS SP3 dev image upgraded to 6.0 and I got this same error. Now I'm trying it on an exclusively 6.1 vanilla dev image w/ a 4.5 PlumDB moved to the images sql 2005 server for upgrading. Trying both scenarios yields the same results.
My co-worker who's in charge of upgrading collab from 2.x to 4.x had a successful portal db upgrade yesterday from 4.x to 5.x because collab's upgrade path forced him to. I'm wondering if we just don't want to do the same thing for our portal db upgrade - i.e not follow the 4.5 to 6 path and just chugging it through the 4 to 5 to 6 path. Argh.
I'll continue looking into the environment variable situation then probably go back to my original 4.5WS SP3 dev imagej and try the upgrade from scratch again.
This is really eating into time we alotted for ui changes - db wasn't supposed to take this long. :(

Remote portlets

is anybody familiar with "remote portlets"? is there any documentation about it? thanks!

Hello,
I read your topic on dev2dev.
We are in phase of BEA portal investigation, and ask ourself which web framework to use : struts, netui, JSF.
The architecture we want to implement is something like:
standard web app in a simple producer server, which will exposed portlet to a portal container.
In fact we are interesting by JSF, but not sure about the good integration in wlp.
What is your feedback about the integration of JSF in BEA Portal (using pageflow)? Is it stable? Which type of problems do you have?
Are you also happy with WSRP?
Thanks a lot for your infos.
Have a good day,
Yves Jusot

EJB Security Volation when access WSRP remote portlet

I have set up a portal server using Workshop 8.1.3 and made it a producer of an remote portlet. I turn off the registration by setting it in wsrp-producer-config (<registration required="false" secure="false"/>). I have tested this remote portlet by accessing it from another Weblogic portal site.
What I really want to do is to use this remote portlet on a MS sharepoint portal site (with WSRP Web Part Toolkit for sharepoint, http://www.gotdotnet.com/workspaces/workspace.aspx?id=2e3d8a57-ec9f-4d16-9a81-a395679d6392). I think I can successfully connected to the weblogic portal site, but I get a security volation error:
Error: [EJB:010160]Security Violation: User: '' has insufficient permission to access EJB: type=, application=Demo, module=netuix.jar, ejb=PortalCustomizationManager, method=createSuccessor, methodInterface=Remote, signature={com.bea.netuix.application.manager.CustomizationContext,com.bea.netuix.application.identifier.DesktopDefinitionId,com.bea.netuix.application.identifier.PortletInstanceId}.
Can any one tell me what I need to do to pass this security volation??
Thank you very much.

Thanks Subbu, this is what I am looking for, a way to get the requests and responses. I got the request/response from SOAP monitor. However I can't tell why it's not working (why the consumer doesn't have insufficient access). From the registration and service description, I can't tell anything wrong as they don't require any addition information for the consumer. I'll paste all the SOAP message between my consumer/producer and please let me know if you notice anything wrong. The SOAP messages are in order. Thanks so much for your help.
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body>
<register xmlns="urn:oasis:names:tc:wsrp:v1:types">
<consumerName>wsrpConsumer</consumerName>
<consumerAgent>wsrpConsumer.1.1</consumerAgent>
<methodGetSupported>false</methodGetSupported>
</register>
</soap:Body>
</soap:Envelope>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<urn:registerResponse xmlns:urn="urn:oasis:names:tc:wsrp:v1:types">
<urn:registrationHandle>28011</urn:registrationHandle>
</urn:registerResponse>
</soapenv:Body>
</soapenv:Envelope>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body>
<getServiceDescription xmlns="urn:oasis:names:tc:wsrp:v1:types">
<registrationContext>
<registrationHandle>28011</registrationHandle>
</registrationContext>
</getServiceDescription>
</soap:Body>
</soap:Envelope>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<urn:getServiceDescriptionResponse xmlns:urn="urn:oasis:names:tc:wsrp:v1:types"> <urn:requiresRegistration>true</urn:requiresRegistration>
<urn:offeredPortlets> <urn:portletHandle>portlet_1</urn:portletHandle>
<urn:markupTypes>
<urn:mimeType>text/html</urn:mimeType>
<urn:modes>wsrp:view</urn:modes>
<urn:windowStates>wsrp:normal</urn:windowStates>
<urn:locales>en</urn:locales>
<urn:locales>en-US</urn:locales>
</urn:markupTypes>
<urn:groupID>WSRPDemo</urn:groupID>
<urn:description xml:lang="en-US">
<urn:value/>
</urn:description>
<urn:shortTitle xml:lang="en-US">
<urn:value>pageFlowPortlet</urn:value>
</urn:shortTitle>
<urn:title xml:lang="en-US">
<urn:value>pageFlowPortlet</urn:value>
</urn:title>
<urn:displayName xml:lang="en-US">
<urn:value>pageFlowPortlet</urn:value>
</urn:displayName>
<urn:usesMethodGet>true</urn:usesMethodGet>
<urn:templatesStoredInSession>true</urn:templatesStoredInSession> <urn:doesUrlTemplateProcessing>true</urn:doesUrlTemplateProcessing>
</urn:offeredPortlets> <urn:requiresInitCookie>perGroup</urn:requiresInitCookie>
<urn:registrationPropertyDescription/>
<urn:locales>en</urn:locales>
<urn:locales>en-US</urn:locales>
</urn:getServiceDescriptionResponse>
</soapenv:Body>
</soapenv:Envelope>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body>
<clonePortlet xmlns="urn:oasis:names:tc:wsrp:v1:types">
<registrationContext>
<registrationHandle>28011</registrationHandle>
</registrationContext>
<portletContext>
<portletHandle>portlet_1</portletHandle>
</portletContext>
<userContext>
<userContextKey>wsrpConsumer</userContextKey>
</userContext>
</clonePortlet>
</soap:Body>
</soap:Envelope>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<soapenv:Fault xmlns:urn="urn:oasis:names:tc:wsrp:v1:types">
<faultcode>urn:OperationFailed</faultcode>
<faultstring>[EJB:010160]Security Violation: User: '<anonymous>' has insufficient permission to access EJB: type=<ejb>, application=Demo, module=netuix.jar, ejb=PortalCustomizationManager, method=createSuccessor, methodInterface=Remote, signature={com.bea.netuix.application.manager.CustomizationContext,com.bea.netuix.application.identifier.DesktopDefinitionId,com.bea.netuix.application.identifier.PortletInstanceId}.</faultstring>
<detail>
<urn:OperationFailed/>
<urn1:FaultDetail xmlns:urn1="urn:bea:wsrp:wlp:v1:types">
<urn1:created>2004-09-27T11:37:09.648-04:00</urn1:created>
<urn1:trace>com.bea.wsrp.faults.OperationFailedException: [EJB:010160]Security Violation: User: '<anonymous>' has insufficient permission to access EJB: type=<ejb>, application=Demo, module=netuix.jar, ejb=PortalCustomizationManager, method=createSuccessor, methodInterface=Remote, signature={com.bea.netuix.application.manager.CustomizationContext,com.bea.netuix.application.identifier.DesktopDefinitionId,com.bea.netuix.application.identifier.PortletInstanceId}.
     at com.bea.wsrp.producer.adapter.customization.PortalCustomizationServiceAdapter.clonePortlet(PortalCustomizationServiceAdapter.java:264)
     at com.bea.wsrp.producer.handlers.management.PortletManagementServiceHandler.doClonePortlet(PortletManagementServiceHandler.java:247)
     at com.bea.wsrp.producer.handlers.management.PortletManagementServiceHandler.doService(PortletManagementServiceHandler.java:152)
     at com.bea.wsrp.producer.handlers.AbstractServiceHandler.service(AbstractServiceHandler.java:92)
     at com.bea.wsrp.producer.WsrpServer.processServiceRequest(WsrpServer.java:283)
     at com.bea.wsrp.producer.WsrpServer.service(WsrpServer.java:168)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:996)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
     at com.bea.wsrp.producer.adapter.pageflow.WsrpPageflowFilter.doFilter(WsrpPageflowFilter.java:73)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
     at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:351)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6458)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3661)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2630)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)</urn1:trace>
</urn1:FaultDetail>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>

Facing problem working with remote portlets

Hi,
I have a usecase where in i created a WSRP producer containing 2 jsr168 portlets. This producer application contains a form based security configured for the default role PortalSystemAdministrator(weblogic/weblogic).
I am have a consumer application which consumes these portlets. This application too has form based security configured for the default role PortalSystemAdministrator.
What i have done in the above application is created a SSO scenario, where in once i login in through the consumer application, the user information is passed along to the producer through the configured WSRPIdentityAsserter token, thereby forming a trust between the producer and consumer application.
This scenario works perfectly fine as expected and i am able to view the remote portlets through the consumer.
Now i have deployed another j2ee application in the same portal domain. This application resulted in a custom realm created and a set of custom authentication providers within it.
So now the current situation is that active realm in the new custom realm, and it contains 4 custom suthentication providers. Here i saw the WSRPIdentityAsserter missing from the list so from the admin console i configured WSRPIdentityAsserter.
But when i try to run the same consumer application, though it lets me login in using the same credentials (weblogic/weblogic), it fails to propagate the principal values across to the producer application.
Since in my producer portlet i have a code "request.getUserPrincipal()" which now results in a null value.
When i used the "/monitor" context to check for the flow of soap messages between the consumer and the producer i can see the header containing the Saml token and "weblogic" as the user name.
And the most wired part about all this is, when i was reading through the weblogic documentation for wsrp, i encountered something related to <enable-local-proxy> value within wsrp-producer-registry.xml. By default this value is set to false. And the things worked well earlier with this default value as explained above. So just to give a shot at trying things i set this value to true and i was able to view the portlets correctly.
But i am still yet to find a solution to the problem as stated above with the <enable-local-proxy> set to its default value(false), since it worked well earlier.
So i am pretty clueless as to what would be going wrong here. Is it that since the new custom relam is now active i need to make some sort of changes in regards to the WSRPIdentityAsserter configurations.
I tried googling for a long time, but failed to get any relevant help on this problem.
Can someone please throw some light on this.
Thanks,
Vikram

Deepak,
I dont think that would be an issue since, my scenario worked well with the default realm (myrealm) and the default user (weblogic/weblogic). In that case i suppose it used DefaultAuthenticator for authentication and WSRPIdentityAsserter for passing the information from the consumer to the producer.
But after deploying this other J2ee application on the same portal domain, which resulted in a new security realm being created and few custom authentication providers added.
So now the situation is when i try to run the above consumer application, though it lets me login but it does not pass the login credentials (principal) to the producer application (which is earlier did through the WSRPIdentityAsserter). Since my code in the producer portlet (request.getUserPrincipal()) results in null value.
Checking through the "/monitor" context shows that the consumer is passing the login credentials through the saml tokens within the SOAP header. But either it is not reaching the producer application or then there is some other reason due to which the producer application is failing to trust the consumer and provide the secure data.
Please can some one help me on this.
Thanks,
Vikram

Overriding or Adding CSS on a remote portlet

Hi all,
I have a producer portlet on Jboss and a remote consumer portlet on Weblogic Portal 10.2. I want to override or add the CSS on the consumer side to that portlet . I tried by giving the same path of the CSS file in both consumer and producer.
Please tell me if there is any way to do that.
Thanks
V.K. Singla

In G6, we have provided a way for a remote portlet to grab the parameters from the URL. If you go to the user info page for the web service, you will see a new option: "Host Page URL Query String". If you check that box, the remote tier will get the full query string, as typed into the browser, as a user info parameter. You can then parse that query string and get any additional arguments that you have passed in.
We realize that this will not work in 5.x, which most of you use. Below you will find the code that you can put into your 5.0 portaluiinfrastructure.jar/dll to make the same change as what we did with G6. That way, if you write your portlets to this feature now, when you upgrade to G6 they will continue working and you shouldn't have to do any modifications to the portal UI.
Locate AppDataObject file, which should be in portaluiinfrastructure.statichelpers package. Find this function:
public static IPTState GetAppDataObject(int iCommunityID, int iPageID, int iGWParams, String strHostPageURI, AActivitySpace asOwner, boolean bResolveSecureBase)
It should be a pretty long function that adds all sorts of stuff to objAppDataObject. At the very end of this function, immediately before the log.Debug statements, add the following line of code:
//set the query string on UserInfoptSession.GetUserInfo().AddUserInfoSetting("HostPageQueryString", asOwner.GetCurrentHTTPRequest().GetQueryString());
Build and deploy a new portaluiinfrastructure.jar/dll according to instructions published on the dev center.
Start the portal, open the web service object corresponding to the portlet which should have access to query string parameters from the URL. On the User Info page, add user info setting name "HostPageQueryString". In your portlet, get the user info setting with that name - you will have the query string as entered in the browser.
Feel free to post in this thread if you encounter any difficulties with this approach.

Federation of user properties

Hello,
Have anybody got the federation of user properties from a consumer portlet to a producer portlet to work in portal 9.2?
I have the following setup:
- 2 portal web applications running on Windows XP
in 2 different domains
- both web apps has UserProperties.usr userprofile defined, with one property; "testProperty"
- The federated portlet is a JSP portlet the uses <profile:getProperty> to display the value of "testProperty"
- In producer web app I have created a wsrp-producer-config.xml file in the WEB-XML folder, and specified:
<requiredUserProperties properties="all"/>
The problem is that the when displayed in the consumer, the federated portlet is always displaying the default property value for "testProperty" defined on the producer, never the value from the consumer.
No error messages...
Has anybody else gotten a similar setup to work?
Regards,
oyvind

Can you check the proxy portlet (the .portlet file) created on the
consumer. Does it have any user property related elements.
Subbu
Oyvind Johansen wrote:
Hello,
Have anybody got the federation of user properties from a consumer portlet to a producer portlet to work in portal 9.2?
I have the following setup:
- 2 portal web applications running on Windows XP
in 2 different domains
- both web apps has UserProperties.usr userprofile defined, with one property; "testProperty"
- The federated portlet is a JSP portlet the uses <profile:getProperty> to display the value of "testProperty"
- In producer web app I have created a wsrp-producer-config.xml file in the WEB-XML folder, and specified:
<requiredUserProperties properties="all"/>
The problem is that the when displayed in the consumer, the federated portlet is always displaying the default property value for "testProperty" defined on the producer, never the value from the consumer.
No error messages...
Has anybody else gotten a similar setup to work?
Regards,
oyvind

Exposing User properties in remote portlet?

Similar Messages

Maybe you are looking for