You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by "Brian Eaton (JIRA)" <ji...@apache.org> on 2008/01/24 19:34:34 UTC
[jira] Created: (SHINDIG-35) Create a demo of a server side
container
Create a demo of a server side container
----------------------------------------
Key: SHINDIG-35
URL: https://issues.apache.org/jira/browse/SHINDIG-35
Project: Shindig
Issue Type: New Feature
Components: Gadgets Server - Java
Reporter: Brian Eaton
Assignee: John Hjelmstad
I'd like Shindig to have a sample implementation of a server-side container.
I definitely don't want to build any type of robust or scalable user registry to go along with this work. I'd like to see scaffolding, not a lot of implementation.
The ability to store user preferences on the server rather than the client would be a reasonable first milestone. A next milestone would be support for OAuth in gadgets.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-35) Create a demo of a server side
container
Posted by "Brian Eaton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566880#action_12566880 ]
Brian Eaton commented on SHINDIG-35:
------------------------------------
Hi Martin -
You're missing a couple of pieces.
- A demo OAuth service provider: check out the code linked from http://oauth.net. You can run one up with maven pretty easily.
- You need a demo server side container to create the gadget security token. I've hacked something together I like to call "ContainerServlet", it's hosted on /container.
> Create a demo of a server side container
> ----------------------------------------
>
> Key: SHINDIG-35
> URL: https://issues.apache.org/jira/browse/SHINDIG-35
> Project: Shindig
> Issue Type: New Feature
> Components: Gadgets Server - Java
> Reporter: Brian Eaton
> Assignee: John Hjelmstad
> Attachments: oauth.patch, sillyoauthgadget.js, testgadget.xml
>
>
> I'd like Shindig to have a sample implementation of a server-side container.
> I definitely don't want to build any type of robust or scalable user registry to go along with this work. I'd like to see scaffolding, not a lot of implementation.
> The ability to store user preferences on the server rather than the client would be a reasonable first milestone. A next milestone would be support for OAuth in gadgets.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-35) Create a demo of a server side
container
Posted by "Martin Webb (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566871#action_12566871 ]
Martin Webb commented on SHINDIG-35:
------------------------------------
Installed the patch okay. Created the sample widget.
Created the following sample container to host the widget:
<!DOCTYPE html>
<html>
<head>
<title>Sample: settitle support</title>
<!-- default container look and feel -->
<link rel="stylesheet" href="gadgets.css">
<script type="text/javascript" src="json.js"></script>
<script type="text/javascript" src="ifpc.js"></script>
<script type="text/javascript" src="cookies.js"></script>
<script type="text/javascript" src="gadgets.js"></script>
<script type="text/javascript">
var specUrl0 = 'http://www.btinternet.com/~martin.webb/google-gadgets/oauth.xml';
function init() {
gadgets.container.layoutManager =
new gadgets.FloatLeftLayoutManager('gadget-parent');
gadgets.container.setParentUrl('ifpc_relay.html');
var gadget = gadgets.container.createGadget({specUrl: specUrl0});
gadget.setServerBase('http://localhost:9090/gadgets/');
gadgets.container.addGadget(gadget);
};
function renderGadgets() {
gadgets.container.renderGadgets();
};
</script>
</head>
<body onLoad="init();renderGadgets()">
<h2>Sample: settitle support</h2>
<div>(Requires a Shindig server running at http://localhost:9090)</div>
<div id="gadget-parent" class="gadgets-gadget-parent"></div>
</body>
</html>
Pasted the sillyauthgadet.js into the form and then submit:
Error: data has no properties
Source File: http://localhost:9090/gadgets/ifr?url=http%3A%2F%2Fwww.btinternet.com%2F~martin.webb%2Fgoogle-gadgets%2Foauth.xml&synd=gadgets&mid=0&parent=http%3A%2F%2Flocalhost%3A9090%2Fgadgets%2Fcontainer%2Fifpc_relay.html%3F&ogc=localhost:9090
Line: 805
Is the shindig instance supposed to be running on the same host/port as the oauth-provider? I guess because its a proxy implementation it does not matter? But, is there a real implementation of (other than a proxy?):
http://localhost:9090/oauth-provider/echo
http://localhost:9090/oauth-provider/request_token
http://localhost:9090/oauth-provider/authorize
http://localhost:9090/oauth-provider/access_token
... or is that to come (as a separate oauth-provider web-app)?
So a read of the code (and watching what it does) suggests that the widget executes the pasted sample JS. This makes a call to the core/io.makeRequest method. Passing
AUTHENTICATED and sample
a proxy call is made to the proxy url on the server at:
proxy?url=http%3A%2F%2Flocalhost%3A9090%2Foauth-provider%2Fecho&output=js&auth=AUTHENTICATED&providerNick=sample
passing a X-Gadget-Security-Token header set to ? Appears to be undefined?
the proxyHandler extracts the url from the query string, and then the auth param, and then the X-Gadget-Security-Token hdr.
Which throws the exception:
2008-02-08 00:36:09.680::WARN: /gadgets/proxy
java.lang.NullPointerException
at org.apache.shindig.security.BlobCrypter.webSafeBase64Decode(BlobCrypter.java:92)
at org.apache.shindig.security.BlobCrypter.unwrap(BlobCrypter.java:144)
at org.apache.shindig.security.BlobCrypter.unwrapProperties(BlobCrypter.java:217)
at org.apache.shindig.gadgets.BasicGadgetToken.fromSerialForm(BasicGadgetToken.java:53)
at org.apache.shindig.gadgets.BasicGadgetTokenSigner.createToken(BasicGadgetTokenSigner.java:55)
at org.apache.shindig.gadgets.http.ProxyHandler.buildSigner(ProxyHandler.java:134)
at org.apache.shindig.gadgets.http.ProxyHandler.fetchJson(ProxyHandler.java:70)
at org.apache.shindig.gadgets.http.ProxyServlet.doGet(ProxyServlet.java:50)
<snip>
I think a null or an empty string is passed into BasicGadgetTokenSigner.createToken() as the X-Gadget-Security-Token was undefined?
> Create a demo of a server side container
> ----------------------------------------
>
> Key: SHINDIG-35
> URL: https://issues.apache.org/jira/browse/SHINDIG-35
> Project: Shindig
> Issue Type: New Feature
> Components: Gadgets Server - Java
> Reporter: Brian Eaton
> Assignee: John Hjelmstad
> Attachments: oauth.patch, sillyoauthgadget.js, testgadget.xml
>
>
> I'd like Shindig to have a sample implementation of a server-side container.
> I definitely don't want to build any type of robust or scalable user registry to go along with this work. I'd like to see scaffolding, not a lot of implementation.
> The ability to store user preferences on the server rather than the client would be a reasonable first milestone. A next milestone would be support for OAuth in gadgets.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHINDIG-35) Create a demo of a server side
container
Posted by "Brian Eaton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Eaton updated SHINDIG-35:
-------------------------------
Attachment: oauth.patch
After looking at this for a bit I decided that OAuth might actually be easier than user preferences. I'm uploading a patch that adds some rudimentary OAuth support to Shindig as well as the skeleton of a server-side container.
Elements in this patch (which probably needs to be broken into smaller chunks to make merging it in less of a big bang...)
ProxyHandler support for signing requests: this ends up conflicting slightly with Louis's recent patch for signed fetch, but not by much.
RemoteContentFetcher support for adding HTTP headers to requests.
Real crypto for gadget tokens: BlobCrypter encrypts and signs the data.
Tighter URL validation, so Shindig is less of an open proxy (but is still fairly dangerous in this respect...)
Some dependency injection that we might be able to show to people who want to know how to glue together their container and Shindig.
I'm interested in feedback on which parts of this are sane, which are crazy, and how it can best be broken up for inclusion into Shindig.
> Create a demo of a server side container
> ----------------------------------------
>
> Key: SHINDIG-35
> URL: https://issues.apache.org/jira/browse/SHINDIG-35
> Project: Shindig
> Issue Type: New Feature
> Components: Gadgets Server - Java
> Reporter: Brian Eaton
> Assignee: John Hjelmstad
> Attachments: oauth.patch
>
>
> I'd like Shindig to have a sample implementation of a server-side container.
> I definitely don't want to build any type of robust or scalable user registry to go along with this work. I'd like to see scaffolding, not a lot of implementation.
> The ability to store user preferences on the server rather than the client would be a reasonable first milestone. A next milestone would be support for OAuth in gadgets.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHINDIG-35) Create a demo of a server side
container
Posted by "Brian Eaton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Eaton updated SHINDIG-35:
-------------------------------
Attachment: (was: oauth.patch)
> Create a demo of a server side container
> ----------------------------------------
>
> Key: SHINDIG-35
> URL: https://issues.apache.org/jira/browse/SHINDIG-35
> Project: Shindig
> Issue Type: New Feature
> Components: Gadgets Server - Java
> Reporter: Brian Eaton
> Assignee: John Hjelmstad
> Attachments: oauth.patch, sillyoauthgadget.js, testgadget.xml
>
>
> I'd like Shindig to have a sample implementation of a server-side container.
> I definitely don't want to build any type of robust or scalable user registry to go along with this work. I'd like to see scaffolding, not a lot of implementation.
> The ability to store user preferences on the server rather than the client would be a reasonable first milestone. A next milestone would be support for OAuth in gadgets.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHINDIG-35) Create a demo of a server side
container
Posted by "Brian Eaton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Eaton updated SHINDIG-35:
-------------------------------
Attachment: (was: oauth.patch)
> Create a demo of a server side container
> ----------------------------------------
>
> Key: SHINDIG-35
> URL: https://issues.apache.org/jira/browse/SHINDIG-35
> Project: Shindig
> Issue Type: New Feature
> Components: Gadgets Server - Java
> Reporter: Brian Eaton
> Assignee: John Hjelmstad
>
> I'd like Shindig to have a sample implementation of a server-side container.
> I definitely don't want to build any type of robust or scalable user registry to go along with this work. I'd like to see scaffolding, not a lot of implementation.
> The ability to store user preferences on the server rather than the client would be a reasonable first milestone. A next milestone would be support for OAuth in gadgets.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-35) Create a demo of a server side
container
Posted by "Kevin Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565644#action_12565644 ]
Kevin Brown commented on SHINDIG-35:
------------------------------------
Are you sure this is the up to date patch? It looks the same to me.
> Create a demo of a server side container
> ----------------------------------------
>
> Key: SHINDIG-35
> URL: https://issues.apache.org/jira/browse/SHINDIG-35
> Project: Shindig
> Issue Type: New Feature
> Components: Gadgets Server - Java
> Reporter: Brian Eaton
> Assignee: John Hjelmstad
> Attachments: oauth.patch, sillyoauthgadget.js, testgadget.xml
>
>
> I'd like Shindig to have a sample implementation of a server-side container.
> I definitely don't want to build any type of robust or scalable user registry to go along with this work. I'd like to see scaffolding, not a lot of implementation.
> The ability to store user preferences on the server rather than the client would be a reasonable first milestone. A next milestone would be support for OAuth in gadgets.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHINDIG-35) Create a demo of a server side
container
Posted by "Brian Eaton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Eaton updated SHINDIG-35:
-------------------------------
Attachment: oauth.patch
One more try.
> Create a demo of a server side container
> ----------------------------------------
>
> Key: SHINDIG-35
> URL: https://issues.apache.org/jira/browse/SHINDIG-35
> Project: Shindig
> Issue Type: New Feature
> Components: Gadgets Server - Java
> Reporter: Brian Eaton
> Assignee: John Hjelmstad
> Attachments: oauth.patch, sillyoauthgadget.js, testgadget.xml
>
>
> I'd like Shindig to have a sample implementation of a server-side container.
> I definitely don't want to build any type of robust or scalable user registry to go along with this work. I'd like to see scaffolding, not a lot of implementation.
> The ability to store user preferences on the server rather than the client would be a reasonable first milestone. A next milestone would be support for OAuth in gadgets.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-35) Create a demo of a server side
container
Posted by "Martin Webb (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567086#action_12567086 ]
Martin Webb commented on SHINDIG-35:
------------------------------------
Checked out oauth.
did a mvn install on core and example
did a mvn jetty:run on example/oauth-provide and it fails:
martin@martin-desktop:~/repositories/oauth/svn/code/java/example/oauth-provider$ mvn jetty:run
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'jetty'.
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] The plugin 'org.apache.maven.plugins:maven-jetty-plugin' does not exist or no valid version could be found
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Finished at: Fri Feb 08 16:36:13 GMT 2008
[INFO] Final Memory: 1M/9M
[INFO] ------------------------------------------------------------------------
Delete my mvn repo twice tried adding dependencies for jetty - no luck.
Any pointer on what you did to get it running appreciated. This is only my second mvn project.
Martin
> Create a demo of a server side container
> ----------------------------------------
>
> Key: SHINDIG-35
> URL: https://issues.apache.org/jira/browse/SHINDIG-35
> Project: Shindig
> Issue Type: New Feature
> Components: Gadgets Server - Java
> Reporter: Brian Eaton
> Assignee: John Hjelmstad
> Attachments: oauth.patch, sillyoauthgadget.js, testgadget.xml
>
>
> I'd like Shindig to have a sample implementation of a server-side container.
> I definitely don't want to build any type of robust or scalable user registry to go along with this work. I'd like to see scaffolding, not a lot of implementation.
> The ability to store user preferences on the server rather than the client would be a reasonable first milestone. A next milestone would be support for OAuth in gadgets.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHINDIG-35) Create a demo of a server side
container
Posted by "Brian Eaton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Eaton updated SHINDIG-35:
-------------------------------
Attachment: sillyoauthgadget.js
This is the javascript I've been using to test.
> Create a demo of a server side container
> ----------------------------------------
>
> Key: SHINDIG-35
> URL: https://issues.apache.org/jira/browse/SHINDIG-35
> Project: Shindig
> Issue Type: New Feature
> Components: Gadgets Server - Java
> Reporter: Brian Eaton
> Assignee: John Hjelmstad
> Attachments: oauth.patch, sillyoauthgadget.js, testgadget.xml
>
>
> I'd like Shindig to have a sample implementation of a server-side container.
> I definitely don't want to build any type of robust or scalable user registry to go along with this work. I'd like to see scaffolding, not a lot of implementation.
> The ability to store user preferences on the server rather than the client would be a reasonable first milestone. A next milestone would be support for OAuth in gadgets.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-35) Create a demo of a server side
container
Posted by "Brian Eaton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565436#action_12565436 ]
Brian Eaton commented on SHINDIG-35:
------------------------------------
Arg. The patch I attached doesn't have the new files I added, they are stuck on another computer. I'll attach a new patch tonight.
> Create a demo of a server side container
> ----------------------------------------
>
> Key: SHINDIG-35
> URL: https://issues.apache.org/jira/browse/SHINDIG-35
> Project: Shindig
> Issue Type: New Feature
> Components: Gadgets Server - Java
> Reporter: Brian Eaton
> Assignee: John Hjelmstad
> Attachments: oauth.patch
>
>
> I'd like Shindig to have a sample implementation of a server-side container.
> I definitely don't want to build any type of robust or scalable user registry to go along with this work. I'd like to see scaffolding, not a lot of implementation.
> The ability to store user preferences on the server rather than the client would be a reasonable first milestone. A next milestone would be support for OAuth in gadgets.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHINDIG-35) Create a demo of a server side
container
Posted by "Brian Eaton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Eaton updated SHINDIG-35:
-------------------------------
Attachment: testgadget.xml
This is the gadget I've been using to test this.
> Create a demo of a server side container
> ----------------------------------------
>
> Key: SHINDIG-35
> URL: https://issues.apache.org/jira/browse/SHINDIG-35
> Project: Shindig
> Issue Type: New Feature
> Components: Gadgets Server - Java
> Reporter: Brian Eaton
> Assignee: John Hjelmstad
> Attachments: oauth.patch, sillyoauthgadget.js, testgadget.xml
>
>
> I'd like Shindig to have a sample implementation of a server-side container.
> I definitely don't want to build any type of robust or scalable user registry to go along with this work. I'd like to see scaffolding, not a lot of implementation.
> The ability to store user preferences on the server rather than the client would be a reasonable first milestone. A next milestone would be support for OAuth in gadgets.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHINDIG-35) Create a demo of a server side
container
Posted by "Kevin Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Brown updated SHINDIG-35:
-------------------------------
Component/s: (was: Gadgets Server - Java)
Wishlist
Assignee: (was: John Hjelmstad)
Priority: Minor (was: Major)
Unassigning and recategorizing this one since the bulk of this discussion is being broken into separate issues, and because a final implementation decision for how OAuth is going to work hasn't been made yet. We'll want to revisit this at some point in the future. We may want to just close this issue and focus on oauth for now.
> Create a demo of a server side container
> ----------------------------------------
>
> Key: SHINDIG-35
> URL: https://issues.apache.org/jira/browse/SHINDIG-35
> Project: Shindig
> Issue Type: New Feature
> Components: Wishlist
> Reporter: Brian Eaton
> Priority: Minor
> Attachments: oauth.patch, sillyoauthgadget.js, testgadget.xml
>
>
> I'd like Shindig to have a sample implementation of a server-side container.
> I definitely don't want to build any type of robust or scalable user registry to go along with this work. I'd like to see scaffolding, not a lot of implementation.
> The ability to store user preferences on the server rather than the client would be a reasonable first milestone. A next milestone would be support for OAuth in gadgets.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-35) Create a demo of a server side
container
Posted by "Martin Webb (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567253#action_12567253 ]
Martin Webb commented on SHINDIG-35:
------------------------------------
Was able to successfully do a "mvn jetty:run" to get the ouath-provider example web app running with the following patches:
Index: /home/martin/repositories/oauth/svn/code/java/example/oauth-provider/pom.xml
===================================================================
--- /home/martin/repositories/oauth/svn/code/java/example/oauth-provider/pom.xml (revision 470)
+++ /home/martin/repositories/oauth/svn/code/java/example/oauth-provider/pom.xml (working copy)
@@ -22,7 +22,7 @@
<build>
<sourceDirectory>src</sourceDirectory>
<testSourceDirectory>test</testSourceDirectory>
- <pluginManagement>
+ <!-- pluginManagement -->
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
@@ -38,7 +38,7 @@
<scanIntervalSeconds>10</scanIntervalSeconds>
<webAppSourceDirectory>${basedir}/web</webAppSourceDirectory>
<webXmlFile>${basedir}/web/WEB-INF/web.xml</webXmlFile>
- <contextPath>/provider</contextPath>
+ <contextPath>/oauth-provider</contextPath>
<connectors>
<connector implementation="org.mortbay.jetty.nio.SelectChannelConnector">
<port>9090</port>
@@ -54,6 +54,14 @@
</configuration>
</plugin>
</plugins>
- </pluginManagement>
+ <!-- /pluginManagement -->
+ <resources>
+ <resource>
+ <directory>src</directory>
+ <includes>
+ <include>**/*.properties</include>
+ </includes>
+ </resource>
+ </resources>
</build>
</project>
Now off to explore the SHINDIG-35 patch in detail - it looks like a humdinger...
> Create a demo of a server side container
> ----------------------------------------
>
> Key: SHINDIG-35
> URL: https://issues.apache.org/jira/browse/SHINDIG-35
> Project: Shindig
> Issue Type: New Feature
> Components: Gadgets Server - Java
> Reporter: Brian Eaton
> Assignee: John Hjelmstad
> Attachments: oauth.patch, sillyoauthgadget.js, testgadget.xml
>
>
> I'd like Shindig to have a sample implementation of a server-side container.
> I definitely don't want to build any type of robust or scalable user registry to go along with this work. I'd like to see scaffolding, not a lot of implementation.
> The ability to store user preferences on the server rather than the client would be a reasonable first milestone. A next milestone would be support for OAuth in gadgets.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHINDIG-35) Create a demo of a server side
container
Posted by "Brian Eaton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Eaton updated SHINDIG-35:
-------------------------------
Attachment: oauth.patch
New version of the patch, now with added files!
> Create a demo of a server side container
> ----------------------------------------
>
> Key: SHINDIG-35
> URL: https://issues.apache.org/jira/browse/SHINDIG-35
> Project: Shindig
> Issue Type: New Feature
> Components: Gadgets Server - Java
> Reporter: Brian Eaton
> Assignee: John Hjelmstad
> Attachments: oauth.patch
>
>
> I'd like Shindig to have a sample implementation of a server-side container.
> I definitely don't want to build any type of robust or scalable user registry to go along with this work. I'd like to see scaffolding, not a lot of implementation.
> The ability to store user preferences on the server rather than the client would be a reasonable first milestone. A next milestone would be support for OAuth in gadgets.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.