Hi Pushpalanka,
I managed to setup the development environment and build all the sources
(thanks to Omindu :))
Then I made the PEP client using the entitlement stubs as you have
mentioned in a previous thread. It's working in an accepted state. But I
encountered some questions during the process,
Hi all,
With the previous suggestions i'm currently working on having Swagger
integrated to the service. According to the Apache CXF documentation [1]
Swagger can be implemented easily by using its Swagger2Feature library. But
their documentation provides no integration details.
So i integrated t
Hi all,
To update on the current status
1) The endpoint is fully compliant with the XACML REST profile as stated
here [1]
2) It is also in accordance with the JSON XACML request/response profile as
stated in [2], except few things that require changes to balana
3) Developer documentation was gener
UPDATE
Adding missing links
[1]
http://docs.oasis-open.org/xacml/xacml-rest/v1.0/csprd03/xacml-rest-v1.0-csprd03.html
[2]
http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/xacml-json-http-v1.0.html
[3] http://manzzup.github.io/wso2-entitlement-endpoint/devdoc
On Thu, Aug 11, 2016 at 1:22 PM,
Hi Manujith,
Good to see the project reaching final stages.
Please find the comments inline.
Thanks,
Pushpalanka
On Thu, Aug 11, 2016 at 1:23 PM, Manujith Pallewatte
wrote:
> UPDATE
>
> Adding missing links
> [1] http://docs.oasis-open.org/xacml/xacml-rest/v1.0/csprd03
> /xacml-rest-v1.0-csprd
Hi Pushpalanka,
Thank you for the comments
1) I added a list of required changes at [1]
2) The blog post will be link for now from the github readme, since I'm
adding additional blog posts to support the content of the above post
(mostly in depth implementation details for source), I thought of
Hi all,
Coming to the conclusion of the project, here's the progress so far
The project description can be seen at [1]. The goal was to provide RESTful
access to the PDP of the IS
Progress
1) REST implementation done using Apache CXF framework
2) JSON compatibility added using Jackso
Great work Manujith! Let's schedule a demo and a code review within next
week.
Regards,
Omindu.
On Tue, Aug 23, 2016 at 2:27 PM, Manujith Pallewatte
wrote:
> Hi all,
>
> Coming to the conclusion of the project, here's the progress so far
> The project description can be seen at [1]. The goal wa
First sorry about asking this in last minute. We can we find API definition
for this API?
Have we documented somewhere with all requests paths, payloads responses
etc? I
Thanks,
sanjeewa.
On Tue, Aug 23, 2016 at 3:05 PM, Omindu Rathnaweera wrote:
> Great work Manujith! Let's schedule a demo and
Thank you Omindu!
I'll check back for the review date and time
Sanjeewa, the API definition can be found at [1] and it also has a swagger
definition available at the url [2] once the service is running. So a
client can use that.
Thank You
Manujith
[1] https://manzzup.atlassian.net/wiki/display/
Hi Manujith,
Good progress in getting familiar with the environment.
So let's try to start with the scope of the project too.
Since we are to work on implementing REST service, it is better to go
through WSO2 guidelines for REST service implementation. Please find the
white paper at[1] and the re
Hi all,
To update on the progress so far, after having a chat with Pushpalanka, I
started with the project code. Basic setups are done.
Necessary entry points for the service was identified and now I'm familiar
with the process of deploying the REST service as a Web app to the IS.
Right now, the
Hi all,
So I have roughly finished up the following 5 services in REST
getDecision
getDecisionByAttibutes
getBooleanDecision
getEntitledAttributes
getAllEntitlements
The service is packed to a war file deployable to IS 5.2.0
It's still in primary testing, so once it's confirmed working it will be
Hi Manujith,
Please share the code progress via Github, once you are satisfied with
refactoring.
Please fork [1] to your private repo, and at location [2], you may have a
new component named 'org.wso2.carbon.identity.entitlement.endpoint' where
the implementation can reside.
[1] - https://github.
Hi all,
After a bit of refactoring I added the code to [1]. Please feel free to
check the source and give your ideas to improve, specially on the service
related code. All the service related code is available at [2]
Also Omindu tested the initial war file and reported several issues with
it, hop
Hi Manujith,
Better if you can clean up the unnecessary code and do some code
refactoring. We can do another round of testing once you fix the issues I
have mention. You can use the attached Idea Code Formatting Template [1].
To apply the template, follow the steps below.
1. In IDEA settings, go
Hi Manujith,
The IDE specific files(.iml) or code can be removed from the repository.
Once the code refactoring is done and code is cleaned please feel free to
send the PR. Then we can easily comment on the code.
Thanks,
Pushpalanka
On Tue, Jun 7, 2016 at 10:12 AM, Omindu Rathnaweera wrote:
>
Adding a .gitignore to the repo will be the easiest way to keep the
unwanted files away from the repo. See [1].
[1] -
https://github.com/wso2/carbon-identity-framework/blob/master/.gitignore
Regards,
Omindu
On Tue, Jun 7, 2016 at 10:26 AM, Pushpalanka Jayawardhana
wrote:
> Hi Manujith,
>
> The
Hi all,
Code is almost all refracted (apart from the part where authenticators are
hard coded) and it' is available at [1]
I have attached a readme so everyone can help with testing it. But there's
still an issue remaining to debug with the *entitled-attribs *service call,
that came up in prelimin
On Tue, Jun 7, 2016 at 11:01 AM, Manujith Pallewatte
wrote:
> Hi all,
>
> Code is almost all refracted (apart from the part where authenticators are
> hard coded) and it' is available at [1]
> I have attached a readme so everyone can help with testing it. But there's
> still an issue remaining to
Hi Pushpalanka,
Was confused in the PR procedure, and figured that I forgot to initialize
the github repo as you have mentioned in a previous message.
So the new location of the codebase is at [1]
Over the weekend, I'll fix any remaining issues and send the PR
For now I have used the wso2-codestyl
Hi Manujith,
Please have a look at WSO2 REST API guideline [1]. This will help you to
improve the URL nameing.
[1] http://wso2.com/whitepapers/wso2-rest-apis-design-guidelines/
On Thu, Jun 9, 2016 at 3:49 PM, Manujith Pallewatte
wrote:
> Hi Pushpalanka,
>
> Was confused in the PR procedure, an
Hi Manuranga,
I did referred to the guidelines, but was not successful in figuring out
suitable end point names. So Pushpalanka suggested to take community's
ideas in naming them. Any pointers as for which I can improve the names?
According to the guide it says to identify the resources first
Goin
Hi all,
After refactoring and reviewing code using above suggestions, I added a PR,
which can be found at [1]
Regards,
Manujith
[1] https://github.com/wso2/carbon-identity-framework/pull/282
On Sat, Jun 11, 2016 at 12:52 PM, Manujith Pallewatte wrote:
> Hi Manuranga,
>
> I did referred to the
Hi all,
We had the mid-evaluation review, and I've summarized the key points
discussed here
1) Prioritize on the complete JSON implementation for all 5 services methods
2) Comply the service fully with XACML 3.0 REST specification (Read on the
spec and get a firm understanding on all key concepts
Good Work Manujith!
Adding to this. Figure out a way to drop null values from the JSON response
with Jackson level configurations. Also have a look at XACML JSON profile
[1]. It will have guidelines on dealing with JSON inputs/outputs.
[1] -
http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/x
Hi all,
So to start working on the points discussed in the mid evaluation, first is
to align the service with the REST profile of XACML 3.0 [1]
But according to the spec only the following 2 resources are defined
1) home - entry point for REST service, returns links to other resources
2) pdp - re
Hi Manujith,
Please find the comments in line.
On Mon, Jul 4, 2016 at 8:11 PM, Manujith Pallewatte
wrote:
> Hi all,
>
> So to start working on the points discussed in the mid evaluation, first
> is to align the service with the REST profile of XACML 3.0 [1]
> But according to the spec only the
When we are implementing the REST profile XACML - can we implement it as a
microservice on MSF4J? It needs to be an independent deployable unit -
which should function with a set of policies loaded from the filesystem...
Can we do this..?
Thanks & regards,
-Prbath
On Mon, Jul 4, 2016 at 11:44 PM,
Hi Pushpalanka,
Thank you for the comments, I'm currently looking into Swagger
Since it's already used in WSO2 API Manager, can i know if it's built on
CXF as well? In that case I can use existing swagger libraries than
introducing new ones. I found Swagger2Feature [1] library as in the Apache
CXF
30 matches
Mail list logo
