labels for JIRA's
by Luke Holmquist
so i was just checking this JIRA out,
https://issues.jboss.org/browse/AGPUSH-1563
which is sort of a "First Contributor" type of issue. What is probably
the best way of communicating that? The Label Field?
i've seen these labels on our OSS projects using github issues. but we are
a bit tied to JIRA, but we should be able to still labels these things as
such.
wdyt?
-Luke
8 years, 3 months
UPS : Errors in Category Insertion
by Vivek Pandey
Hello UPS Team,
I am noticing a strange problem in UPS 1.0.3. The primary key of the table
"category" is out of sync with the sequence "category_seq".
The id column contains negative values too. We are seeing error messages
like
... 76 more
Caused by: org.postgresql.util.PSQLException: ERROR: duplicate key value
violates unique constraint "category_pkey"
Detail: Key (id)=(192524) already exists.
at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorI
mpl.java:2157)
I have attached the complete log for reference.
We are using Postgres 9.3 and wildfly 8.1.0.
Is it a known issue which is fixed in 1.1.0 Final?
I am working to find the root cause and will communicate as soon as I have
one.
Vivek
This message may contain privileged and confidential information and is solely for the use of intended recipient. The views expressed in this email are those of the sender and not of Pine Labs. The recipient should check this email and attachments for the presence of viruses / malwares etc. Pine Labs accepts no liability for any damage caused by any virus transmitted by this email. Pine Labs may monitor and record all emails.
8 years, 3 months
AGPUSH-1047: UPS decoupling from Keycloak
by Bruno Oliveira
Good morning, today I have a conversation with Matthias about the
decoupling for UPS from Keycloak[1]. Also, during the week, I have a
brainstorm on some ideas with Stian, to figure out the better way to
achieve this.
Motivation
The reason why we want to decouple UPS from Keycloak, is due to the fact
that today is not possible to have UPS and Keycloak in a separated
infrastructure. Currently we bundle it. Keycloak is still and will always
be our default security solution.
There’s no intentions or future plans to make use of another security
provider.
Actions items
During these conversations I identified some action items for myself which
I would like to share. Also, I’m going to start to file Jiras under
AGPUSH-1047 umbrella.
1. Create a client cli script using Aesh to link UPS with Keycloak
The script would ask for admin’s username/password or an initial
registration token. After that, the script would make use of the dynamic
client registration service to create the required clients with Keycloak.
2. Themes
For theme definition we have 2 scenarios:
-
Already existent server in use
Nothing will be changed. It’s already an agreement that the current
theme should be neutral and not changed.
-
Brand new instance of Keycloak with UPS theme
For scenarios where people want custom theme from UPS, people can just
deploy it, exactly like described here (
http://keycloak.github.io/docs/userguide/keycloak-server/html/themes.html...
)
3. Creation of roles for clients
For the very first draft I’m planning to just import ups-realm.json (manual
process) and see how it goes.
The ideal is to extend the client registration service on Keycloak to allow
creating roles for a client. For now, let’s just start simple — this can be
tricky and require more discussion/time.
4. Creating of roles for users
Same as item 3, for now assume that user exist with “admin” role. The ideal
is the creation of a super user to access UPS. For now, users can manually
register/import users that can access UPS through the KC admin console.
5. UPS realm
Discussing with Matthias we came up with 2 scenarios:
- Make use of an already existent realm in use
In this scenarios, people want to make use of UPS, but don’t want to have a
new realm dedicated for it. We’re going to make use of the dynamic client
registration against the realm specified.
- Brand new instance of Keycloak with UPS theme
For people willing to have a separated realm not mixed up with master. In
this scenario we provide ups-realm.json as part of documentation or demo
purposes and make use of the dynamic client registration process.
Note: We probably can benefit of item 1 to import the json file if
necessary.
6. Multiple UPS instances with a single instance of KC
It would require to extend the client registration service and some work on
KC. Depending on the time, it can be done. But for now we’re going to
assume that the relationship will be 1:1, into other words, one instance of
UPS and one instance of KC.
For corp scenarios we would end up with:
Test
- testing.ups.mybank.com
- testing.keycloak.mybank.com
Production
- ups.mybank.com
- keycloak.mybank.com
If you have any questions or feedback, I’m listening.
https://issues.jboss.org/browse/AGPUSH-1047
--
- abstractj
8 years, 3 months
Problem on migrating to 1.1.0-Final
by Javornik, Romain
Hello,
I don't really know if this is the right email address for asking question but I give it a try, please redirect me if I'm wrong !
------ Problem in the UnifiedPush Server User Guide ------
Before explaining my problem I want to tell you that something isn't clear enough from my point of view in your migration guide (https://aerogear.org/docs/unifiedpush/ups_userguide/index/#migration-guide).
On the part where you explain the database migration for mysql you write :
MySQL
Inside of the extracted zip file, there is a liquibase-mysql-example.properties, copy that to liquibase.properties.
cp liquibase-mysql-example.properties liquibase.properties
Once done, you need to edit the new file to match your database name and credentials.
The problem with this is that you can't choose the version you want to upgrade to.
Since I have "changeLogFile=liquibase/master.xml" in my liquidbase.properties, the only upgrade I was able to make was to the 1.0.0-Final and I'm on the 1.0.2.
I had to open the ups-migrator.jar (wich wasn't really userfriendly) to see what was my option. And then I was able to go the version I want (exemple -> "changeLogFile=liquibase/1.1.0-Final/releasechanges.xml")
To conclude I think that just a small explanation in the migration guide will make everything more clear.
------ My migration problem ------
I'm currently using AerogearPush Server 1.0.2 and I want to go to the 1.1.0-Final version.
I download the last package (1.1.0-Final) on this page https://aerogear.org/getstarted/downloads
Like explain above I had some trouble make it work to move to the version I wanted.
Right now in 1.0.2 I can use the Migrator Tool to make sure that my 1.0.2 Mysql database is good and to upgrade it to 1.0.3.
But I can't go the 1.1.0-Final, I join to this email the error I get from the Migrator Tool.
Can you please tell me where the problem might come from or if you have any solution ?
Best Regards,
Romain
8 years, 3 months
Push customization with Android background App
by Bourillon, Matthias
Hello,
I have carefully read and applied the procedure to use Aerogear Push in a Cordova / Ionic App (https://aerogear.org/docs/guides/aerogear-cordova/AerogearCordovaPush/).
Everything is OK except that my onNotification() JS method is not called when my Android App is running in background. The notification is displayed as it arrives and I am not able to apply any logic before it reaches the notification bar.
We are using push to send some instructions to our App which should not always be displayed as-is to end users. Is there a way to customize or apply some logic when an App is in background? Or is this a limitation we have to deal with?
Thanks,
Matthias
8 years, 3 months
